code ERESOLVE Could not resolve dependency after Vaadin 23.0.16
See original GitHub issueDescription of the bug
Cannot restart my project without a total clean.
On restart I get this error:
2022-09-27 14:07:50.849 INFO 17444 --- [onPool-worker-1] c.v.f.s.frontend.TaskUpdatePackages : using 'C:\Program Files\nodejs\npm.cmd --no-update-notifier --no-audit --scripts-prepend-node-path=true --ignore-scripts install' for frontend package installation
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: mapbox-gl-leaflet@0.0.15
npm ERR! Found: leaflet@1.6.0
npm ERR! node_modules/leaflet
npm ERR! leaflet@"file:frontend/core/local_node_modules/leaflet1.7.1-modified" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer leaflet@"file:frontend/core/local_node_modules/leaflet1.7.1-modified" from mapbox-gl-leaflet@0.0.15
npm ERR! node_modules/mapbox-gl-leaflet
npm ERR! mapbox-gl-leaflet@"0.0.15" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: leaflet@undefined
npm ERR! node_modules/leaflet
npm ERR! peer leaflet@"file:frontend/core/local_node_modules/leaflet1.7.1-modified" from mapbox-gl-leaflet@0.0.15
npm ERR! node_modules/mapbox-gl-leaflet
npm ERR! mapbox-gl-leaflet@"0.0.15" 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.
npm ERR!
npm ERR! See C:\Users\svein\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\svein\AppData\Local\npm-cache\_logs\2022-09-27T14_07_52_300Z-debug-0.log
Expected behavior
Work after restart as in 23.0.16
Minimal reproducible example
Seems that the npm module “file:./frontend/core/local_node_modules/leaflet1.7.1-modified” cause the problem
Versions
Hilla: 23.2.2 Flow: 23.2.2 Java: JetBrains s.r.o. 17.0.2 OS: amd64 Windows 10 10.0 Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36 Live reload: Java active (HotswapAgent): Front end active
Issue Analytics
- State:
- Created a year ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Vaadin upgrade 22.0.2 to 23.0.3 failed - Stack Overflow
Never mind - I did a "Vaadin dance" and then the build worked. And the application - at least on first sight -...
Read more >package.json dependency version mismatching on tutorial ...
hi there, I'm new to vaadin 14 and try to following training to build a vaadin 14 ... npm ERR! code ETARGET npm...
Read more >Vaadin 23 is finally here!
Vaadin 23, the latest platform release, is finally released! Start developing with Vaadin 23 already today!
Read more >Error "Failed to determine 'node' tool." with new Vaadin 14.0.0 ...
[ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:14.0.0.rc9:prepare-frontend (default) on project example: Execution default of goal ...
Read more >Vaadin with Spring Boot not starting
When I now work with it again mvn clean install runs fine but starting application gives me: Failed to find the following imports...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Created #14673 for that
This seems to be working now