npm rocks because a deal manager. Specifically, they protects sandwich-dependencies perfectly: if the my bundle utilizes consult version 2 and several-other-library , however-other-library utilizes request adaptation step 1, the latest resulting dependence graph looks like:
This is certainly, generally, great: today certain-other-library possesses its own backup away from demand v1 it can easily explore, while not preventing my package’s v2 backup. Everybody’s password really works!
The challenge: Plugins
A plugin plan is meant to be used having some other “host” bundle, while it cannot constantly yourself utilize the servers package. There are various examples of it pattern from the Node.js package ecosystem already:
- Grunt plugins
- Chai plugins
- LevelUP plugins
- Show 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