npm rocks because the a deal movie director. In particular, they covers sub-dependencies perfectly: if my package utilizes request adaptation dos and several-other-library , however some-other-library hinges on demand type step one, the fresh new ensuing dependence chart turns out:

It is, essentially, great: now certain-other-collection features its own backup away from demand v1 it may play with, while not preventing my package’s v2 duplicate. Everybody’s code work!

The problem: Plugins

A plugin bundle is intended to be studied with other “host” plan, even though it doesn’t constantly myself make use of the machine package. There are many examples of this trend about Node.js plan environment currently:

• Grunt plugins
• Chai plugins
• LevelUP plugins
• Express middleware
• Winston transfers

Even if you’re not familiar with any of those use cases, surely you recall “jQuery plugins” from back when you were a client-side developer: little