Thursday, 15 November 2018

How do I escape NPM Peer Dependency hell?

Right now, I am getting warnings that one package requires a peer dependency that is a later version of a module I am already using, as well as a few about security vulnerabilities. So I upgrade these packages. And get five warnings that five different modules all want five different versions of the same thing. So I upgrade EVERY package to the latest version. And get even more warnings!Surely this is not how it is supposed to be. How is one supposed to resolve these conflicts?

Submitted November 15, 2018 at 06:11PM by -endjamin-

No comments:

Post a Comment