Duplicate id for the same dependency

I’m playing with Browserify and React today and in my bundle I’m noticing that React is loaded with 2 different dependency number. One is 158 and the other is 314.

In the bundle file, I can see this for 314

314:[function(require,module,exports){
arguments[4][158][0].apply(exports,arguments)
},{"./lib/React":187,"dup":158}]

158 is basically just a shortcut for module.exports = require('./lib/React'); which is 187.

My code is broken because of that, because it loads the dependency twice.

[leftmostcat]

I’m experiencing a similar issue with a module attempting to inject itself into jquery. Removing the duplicate jquery from the module’s node_modules/ directory solved the problem. That said, it seems like browserify recognizes that the packages are duplicated. Why couldn’t it (in the above instance) simply give 158 to the second package require()ing React instead of creating 314 to de-duplicate it?

[giggio]

@chrisirhc It makes no sense that I should have to manually enter the node_modules directory to symlink directories. When you npm install npm resolves the dependencies itself, I should not have to go and manually change things. An example are the jquery plugins. Imagine you install 2 different jquery plugins, each jquery plugin might attach itself to a different jquery instance. This is exactly what you do not expect. This gets even worse as npm and jquery are saying that browserify is the way to go for these plugins, but this setup will simply not work if you use more than one plugin. Until I found browserify-resolutions browserify made itself unusable. This is critical and I am appalled that this issue was closed and letting this go on like that.