npm rocks ! since a deal manager. In particular, they covers sub-dependencies very well: if my bundle depends on consult version dos and some-other-collection , however some-other-library depends on consult type step 1, the new ensuing reliance graph turns out:

This is, basically, great: now certain-other-collection possesses its own backup of consult v1 that it could have fun with, without curbing my personal package’s v2 copy. Everybody’s password works!

The problem: Plugins

A plug-in plan is intended to be studied that have another “host” bundle, while it will not always directly make use of the server package. There are numerous examples of which trend from the Node.js bundle ecosystem currently:

• Grunt plugins
• Chai plugins
• LevelUP plugins
• Display middleware
• Winston transports

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