Sentry/nextjs with [email protected]

[ElSeniorMikael]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using? If you use the CDN bundles, please specify the exact bundle (e.g. bundle.tracing.min.js) in your SDK setup.

@sentry/nextjs

SDK Version

7.3.7

Framework Version

No response

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

npm i [email protected]
npm i @sentry/nextjs@latest

Expected Result

To install node_module

Actual Result

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/next
npm ERR! next@"^13.1.7-canary.8" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^10.0.8 || ^11.0 || ^12.0 || ^13.0" from @sentry/[email protected]
npm ERR! node_modules/@sentry/nextjs
npm ERR! @sentry/nextjs@"7.37.0" 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.

[lforst]

Hi, unfortunately, this is a weird behavior of npm we can't really fix on our end without getting rid of the peerDependency. We defined the peer dependency with ^13 which is accurate but npm apparently doesn't resolve this to prereleases as outlined here.

Since this should work with non-canary versions of Next.js I recommend you simply use --force while you're testing the canary release. (Or you switch to yarn or pnpm)