Sentry installation failed Using NextJs@15.2.2-canary.0

[software-dev12]

Environment

What version are you running? Etc.

Steps to Reproduce

1. Using bash & command prompt, I attempted to run npx @sentry/wizard@latest -i nextjs --saas --org --project javascript-nextjs
2. After npm validated my login, the installation immediately fails.
3. I re-ran the same command two more times, first using the --legacy-peer-deps and then using the --force flag, and it still fails.

Expected Result

I expected to follow the step by step example and finish the installation to be able to utilize sentry

Actual Result

Even after using the force flag, sentry just doesn't work after installing.

This is what I pulled from the log file:

2025-04-12T18_53_35_831Z-eresolve-report
# npm resolution error report

While resolving: banking-app@0.1.0
Found: next@15.2.2-canary.0
node_modules/next
  next@"15.2.2-canary.0" from the root project

Could not resolve dependency:
peer next@"^13.2.0 || ^14.0 || ^15.0.0-rc.0" from @sentry/nextjs@9.12.0
node_modules/@sentry/nextjs
  @sentry/nextjs@"9.12.0" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

[Lms24]

Hey @software-dev12 thanks for writing in! you're right, our peer dependency range in the SDK doesn't allow canary versions. We'll think about adding them in the package.json of the nextjs SDK. But adding the --force-install flag to the wizard should ensure that you can install the SDK package despite the warning.

I re-ran the same command two more times, first using the --legacy-peer-deps and then using the --force flag, and it still fails.

Just to confirm: Did you try running the wizard with --force-install?

[Lms24]

So I looked a bit into if we can somehow specify a peer dependency version range to allow canary releases but unfortnuately, I don't think this is possible.

According to the Node semver documentation:

If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag.

Even the most lenient 15.x peer dep range ('>=15.0.0-0 <16.0.0') does not allow for any pre-release higher than 15.0.0-pre.

The only alternatives would be to

• specify every major/minor/patch-pre number explicitly which is obviously unmaintainable
• mark the peer dep as optional (which it is not)
• remove the peer dep (which is also not great as we rely on the package being installed)

So I don't think we can work around you (or other affected users) having to specify --force (or --force-install when using our wizard).

also cc @lforst since we looked at this together today

I'll leave this issue open until we know that setting these flags works.