-
-
Notifications
You must be signed in to change notification settings - Fork 43
Description
Environment
playground
The error is shown in the log for the 'Install Dependencies' task.
Reproduction
https://codesandbox.io/p/sandbox/pinia-orm-nuxt-install-error-t2yc44
Describe the bug
When following the steps to install @pinia-orm/nuxt, the install fails with unable to resolve dependency tree error. This happens when trying to run npm install @pinia-orm/nuxt --save after installing pinia for nuxt.
Steps
- Create new nuxt project with
npx nuxi@latest init newproject - Install pinia with
npx nuxi@latest module add pinia(https://pinia.vuejs.org/ssr/nuxt.html#installation) - Install @pinia-orm/nuxt with
npm install @pinia-orm/nuxt --save(https://pinia-orm.codedredd.de/guide/nuxt/setup)
Additional context
The error shows that this package is looking for @pinia/nuxt: ^0.5.1 but following the steps above will install @pinia/nuxt: ^0.9.0.
These dependencies can be found in packages/nuxt/package.json so I wonder if it's a simple case of updating these
pinia-orm/packages/nuxt/package.json
Line 42 in 1701f72
| "@pinia/nuxt": "^0.5.1" |
pinia-orm/packages/nuxt/package.json
Line 54 in 1701f72
| "@pinia/nuxt": "^0.5.1", |
The issue is fixed by installing @pinia/nuxt: ^0.5.1 so if that's required I think that should be added to the documentation.
In the reproduction I've added "overrides": { "vue": "latest" } to package.json (a fix mentioned in similar issues 1 2 and in the pinia docs) but it doesn't resolve the issue.
Logs
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found: @pinia/nuxt@0.9.0
npm ERR! node_modules/@pinia/nuxt
npm ERR! @pinia/nuxt@"0.9.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @pinia/nuxt@"^0.5.1" from @pinia-orm/nuxt@1.10.1
npm ERR! node_modules/@pinia-orm/nuxt
npm ERR! @pinia-orm/nuxt@"^1.10.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.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /root/.cache/npm/_logs/2025-01-22T19_44_45_235Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /root/.cache/npm/_logs/2025-01-22T19_44_45_235Z-debug-0.log