npm rocks ! since the a great deal movie director. In particular, it protects sub-dependencies perfectly: in the event that my plan relies on request variation 2 and some-other-collection , but some-other-library depends on consult adaptation 1, the ensuing reliance graph turns out:
This really is, essentially, great: today some-other-library has its own duplicate of consult v1 it can easily fool around with, while not interfering with my personal package’s v2 copy. Everybody’s password works!
The situation: Plugins
A plugin plan is intended to be taken with several other “host” package, even though it cannot constantly physically make use of the machine bundle. There are many types of it pattern on the Node.js plan environment already:
- Grunt plugins
- Chai plugins
- LevelUP plugins
- Show 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