We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
... Otherwise our vaadin project will fail to build:
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: no-name@undefined npm ERR! Found: [email protected] npm ERR! node_modules/leaflet npm ERR! leaflet@"1.6.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer leaflet@"~1.3.1" from [email protected] npm ERR! node_modules/leaflet.markercluster npm ERR! leaflet.markercluster@"1.4.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
The text was updated successfully, but these errors were encountered:
At the moment there's a workaround. From the main folder of the vaadin project, execute: npm i --legacy-peer-deps
Sorry, something went wrong.
No branches or pull requests
... Otherwise our vaadin project will fail to build:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: no-name@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/leaflet
npm ERR! leaflet@"1.6.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer leaflet@"~1.3.1" from [email protected]
npm ERR! node_modules/leaflet.markercluster
npm ERR! leaflet.markercluster@"1.4.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
The text was updated successfully, but these errors were encountered: