Yes, it's something like that: react-plaid-link has a peer dependency of react 16.8. What's the difference? Well, a dependency means that your project needs a library to work. A peerDependency means that your project will be attached (or plugged in) into another project, and it will be run as part of that project.
Starting from npm 7, peerDependencies are automatically installed together with normal dependencies, but if npm finds a version mismatch (like this case), it will abort the installation.
Your solution would be to either:
Downgrade your react version to 16.8, so you comply with react-plaid-link's peer dependency.
Ignore the peer dependency (it may break something though) and just continue with react 17. You can do this with npm install react-plaid-link --legacy-peer-deps.
Wait until the mantainers of react-plaid-link change the peer dependency so that their library supports react 17.
PD: This question was posted a month ago and, since then, the developers have added support for react 17
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Ron!
Yes, it's something like that:
react-plaid-linkhas a peer dependency ofreact 16.8. What's the difference? Well, a dependency means that your project needs a library to work. A peerDependency means that your project will be attached (or plugged in) into another project, and it will be run as part of that project.Starting from npm 7,
peerDependenciesare automatically installed together with normal dependencies, but if npm finds a version mismatch (like this case), it will abort the installation.Your solution would be to either:
react-plaid-link's peer dependency.npm install react-plaid-link --legacy-peer-deps.PD: This question was posted a month ago and, since then, the developers have added support for react 17