-
Notifications
You must be signed in to change notification settings - Fork 77
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
🐛 The bug
@nuxt/scripts@0.13.1 does not support @stripe/stripe-js 8.x.x due to a peer-dependency mismatch.
npm i
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/scripts@0.13.1
npm error Found: @stripe/stripe-js@8.6.0
npm error node_modules/@stripe/stripe-js
npm error dev @stripe/stripe-js@"^8.6.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @stripe/stripe-js@"^7.0.0" from @nuxt/scripts@0.13.1
npm error node_modules/@nuxt/scripts
npm error @nuxt/scripts@"^0.13.1" from the root project
npm error
npm error Conflicting peer dependency: @stripe/stripe-js@7.9.0
npm error node_modules/@stripe/stripe-js
npm error peerOptional @stripe/stripe-js@"^7.0.0" from @nuxt/scripts@0.13.1
npm error node_modules/@nuxt/scripts
npm error @nuxt/scripts@"^0.13.1" from the root project
🛠️ To reproduce
- Create a new Nuxt project.
- Add @nuxt/scripts@0.13.1 and @stripe/stripe-js@8.6.0 to devDependencies.
- Run npm install
-
Error occur
https://stackblitz.com/edit/nuxt-starter-89tyxwat?file=package.json
🌈 Expected behavior
- @nuxt/scripts should support the latest @stripe/stripe-js 8.x.x.
- No peer-dependency conflicts should occur.
ℹ️ Additional context
- Stripe JS v8 is backward-compatible with v7 for client-side usage.
- The fix likely only requires updating the peer dependency range in @nuxt/scripts from "^7.0.0" to "^7 || ^8".
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working