NPM UNMET PEER DEPENDENCY questionmarks-CodePudding

The

Let's say the new module used [email protected] and someone who already had [email protected] as direct or sub-dependency in their project is more likely to face unmet peer dependency on using the new module.

Downgrading the version is not recommended due to possible conflict with other modules. A workaround would be to add resolutions.

Before doing anything, delete your node-modules folder and package-lock.json file. Ensure your package.json dependency has [email protected] and only add popperjs@^1.16.0 if you're sure that other modules in your project are not relying on later versions of popperjs.

Take a look at this article for a good explanation on peer dependencies

If there are other modules that needs other versions of popperjs then in your package.json you could add an additional property at the end like below,

{ ....., "browserify": { "transform": [ [ "babelify" ] ] }, "resolutions": { popperjs: "^1.16.0" } }

Note:- You're not removing the previous version, resolutions will just pin your sub-dependency to the specified version.

Good Read:- https://medium.com/learnwithrahul/understanding-npm-dependency-resolution-84a24180901b

CodePudding user response：

I often try this when nothing makes sense: Removing the node modules folder and Package-lock.json file. Reset the package.json file to the last stable commit using git. Then clear npm cache and run npm install. And at the end try to install the package pretty-checkbox.