Skip to content
New issue

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

"Could not resolve dependency" error #23

Open
ogrotten opened this issue Dec 2, 2022 · 1 comment · May be fixed by #24
Open

"Could not resolve dependency" error #23

ogrotten opened this issue Dec 2, 2022 · 1 comment · May be fixed by #24

Comments

@ogrotten
Copy link

ogrotten commented Dec 2, 2022

Following the instructions in the README results in this pretty quickly:

PS C:\WORKING\Projects\phyle-trials\create-svelte-electron-app> npm i -D @rollup/plugin-commonjs@latest @rollup/plugin-node-resolve@latest rollup@latest rollup-plugin-css-only@latest rollup-plugin-livereload@latest rollup-plugin-svelte@latest rollup-plugin-terser@latest sirv-cli@latest svelte@latest
npm WARN idealTree Removing dependencies.sirv-cli in favor of devDependencies.sirv-cli
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"3.5.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer rollup@"^2.0.0" from [email protected]
npm ERR! node_modules/rollup-plugin-terser
npm ERR!   dev rollup-plugin-terser@"7.0.2" 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 \windowspath\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     \windowspath\_logs\2022-12-02T15_58_13_167Z-debug-0.log

Any plans to move from rollup to vite along with the vanilla svelte?

@xmaayy xmaayy linked a pull request Dec 24, 2022 that will close this issue
@xmaayy
Copy link

xmaayy commented Dec 24, 2022

Either use yarn (it will resolve it for you) or change the package per my PR #24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants