You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see why using Yarn doesn't cause any issues since I found that it handles these peer dependency conflicts differently and reliably well. In this case,
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @awesome-cordova-plugins/[email protected]
npm ERR! node_modules/@awesome-cordova-plugins/core
npm ERR! @awesome-cordova-plugins/core@"^5.44.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @awesome-cordova-plugins/core@"^6.0.1" from @awesome-cordova-plugins/[email protected]
npm ERR! node_modules/@awesome-cordova-plugins/printer
npm ERR! @awesome-cordova-plugins/printer@"^6.4.0" from the root project
Use yarn install instead of npm install
npm install --global yarn then you can run yarn install and you're good to go 👍🏻
Solution 2
If you still want to use npm as the package manager, you can add a --legacy-peer-deps flag when running npm install --legacy-peer-deps
Hi @aaalgieee,
Maayong buntag! :D
The package manager @nedpals used is Yarn.
I have reproduced your issue by using npm, and I got the same issue when I run
npm install
Solution 1
Simply use Yarn as the package manager.
I can see why using Yarn doesn't cause any issues since I found that it handles these peer dependency conflicts differently and reliably well. In this case,
Use
yarn install
instead ofnpm install
npm install --global yarn
then you can runyarn install
and you're good to go 👍🏻Solution 2
If you still want to use npm as the package manager, you can add a
--legacy-peer-deps
flag when runningnpm install --legacy-peer-deps
legacy-peer-deps
Both worked for me. Let me know if this helped you. Thanks!
Originally posted by @aidrecabrera in #10 (comment)
The text was updated successfully, but these errors were encountered: