ARTICLE AD BOX
I run npm create qwik@latest, make my selections, and following that, during installation, I receive this error:
■ npm install failed │ You might need to run "npm install" manually inside the root of the project.I then go into my project directory just created, I run npm install and receive this error:
npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: @eslint/[email protected] npm error Found: [email protected] npm error node_modules/eslint npm error dev eslint@"9.32.0" from the root project npm error peer eslint@"^8.57.0 || ^9.0.0" from [email protected] npm error node_modules/eslint-plugin-qwik npm error dev eslint-plugin-qwik@"^1.19.0" from the root project npm error 1 more (typescript-eslint) npm error npm error Could not resolve dependency: npm error peerOptional eslint@"^10.0.0" from @eslint/[email protected] npm error node_modules/@eslint/js npm error dev @eslint/js@"latest" from the root project npm error npm error Conflicting peer dependency: [email protected] npm error node_modules/eslint npm error peerOptional eslint@"^10.0.0" from @eslint/[email protected] npm error node_modules/@eslint/js npm error dev @eslint/js@"latest" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution.What exactly is causing this error? Am I correct to presume that @eslint/js is the culprit? What sort of fix is needed here? And what exactly is the best fix for this issue?
Thanks
The error is caused by the recent release of [email protected].
The workaround is to revise the @eslint/js version specification (which is currently latest) in devDependencies in package.json. I suggest specifying it to be ^9, though theoretically any number below 10.0.0 will serve to be an effective workaround.
Example workaround in package.json:
"devDependencies": { ... "@eslint/js": "^9", ... },I have made the Qwik dev team aware of this workaround here.
Explore related questions
See similar questions with these tags.
