search

EOSIO / demux-js-postgres

Demux-js Action Handler implementation for Postgres databases
MIT License
11 stars 10 forks source link

Problem with the cyanaudit migration #67

Closed gaboesquivel closed 5 years ago

gaboesquivel commented 5 years ago

@flux627 I'm still having issues with the latest version.

It seems there might be a problem with the cyanaudit migration.

demux-postgres

First tried 4.0.1, now I'm using master with npm link with console.log to debug

rel #65

conr2d commented 5 years ago

This issue is caused by using different version of pg-promise. QueryFile class from different version of pg-promise are incompatible. (vitaly-t/pg-promise#393)

demux-postgres depends on massive@5.7.2 and pg-promise@8.5.3, but demux-eos depends on massive@^5.7.5, so installed massive on root of node_modules and massive on which demux-postgres depends will be different:

├┬massive@5.7.7
│└─pg-promise@8.5.6
├┬demux-postgres@4.0.1
│└┬massive@5.7.2
│ └─pg-promise@8.5.3

I think it would be better to make the dependent version of massive identical on both demux-eos and demux-postgres packages.

flux627 commented 5 years ago

Issue resolved by #69

jasonbert commented 5 years ago

@flux627 closing my own issue as it's a duplicate of this one. I've changed the demux packages to all use edge, which I believe contains your #69 fix.

image

However, massive is coming back as undefined when I attempt to import it.

image

I can definitely see the export in the dist

image

jasonbert commented 5 years ago

Just to add a bit more, if I install massive@5.11.0, which is the version demux-postgre from the develop branch is using, I still get the cyanaudit problem mentioned by @gaboesquivel when using const massive = require("massive")

jasonbert commented 5 years ago

I had to remove default because there is not default property on massive_1

image