Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

v1 driver cannot resolve internal modules

See original GitHub issue

Installed most recent stable version of neo4j-driver today and when I try to launch my app I get the following error message: Module not found: Can't resolve 'dns' in '/app/node_modules/neo4j-driver/lib/v1/internal' (due note I’m using create-react-app and running the command npm run start)

I’ll look into this issue and see if its just a bad publish or something else. Other recommendations would be helpful though.

Issue Analytics

State:
Created 5 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

lutovichcommented, Sep 28, 2018

Hello,

Pre-release 1.7.0-beta02 version of the driver with the fix is now released. It can be installed using npm install --save neo4j-driver@next. Please give it a try and let us know if there are any problems with it and Webpack. Thanks!

1reaction

lutovichcommented, Sep 20, 2018

Dear All,

Module resolution errors seem to be caused by runtime feature detection in the driver. It contains Node and browser environment specific components in one codebase which confuses bundlers. They can’t determine that Node components are unused and obviously fail at compile time when trying to resolve required Node APIs.

Probably the best workaround right now is to include neo4j-web.min.js in index.js as suggested by @P1zz4br0etch3n here.

Mentioned PR should fix the problem and make it possible to use driver with a simple import or require. It will hopefylly go in 1.7 branch and be released in 1.7.0-beta02 available via npm install --save neo4j-driver@next pre-release channel.