Browserify doesn't use project's `node_modules` directory when using symlink

I have a shared module called foo that I include in my project’s node_modules directory via npm link. In the foo module, I have a require('react') statement where ‘react’ is included as a peer dependency in my project’s node_modules. When using Browserify 9.0.8 everything works fine, but upgrading to 11.0.0 I get the error Cannot find module 'react'.

[tomwidmer]

My solution was to build using an npm script like:

"build:js": "NODE_PATH=./node_modules browserify ..."

which means that the react module (and any other peer dependencies) from your app is found when requires (or ES6 imports) happen in the npm linked module(s). Probably doesn’t work on Windows, but adding a ‘set’ or something would probably fix it. It’s a hack, and you should check things do still work when you copy in the module to the node_modules and don’t use NODE_PATH=.

[cvlmtg]

this should fix the problem, i.e. symlink react inside foo to the react that is inside your main app

app
  node_modules
    foo -> ../../foo
    react

foo
  node_modules
    react -> ../../app/node_modules/react