@sentry/nuxt is not working with nuxt + locked vue@3.5.13 (because of memory leak in 3.5.17)

[SebbeJohansson]

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?

@sentry/nuxt

SDK Version

10.11.0

Framework Version

3.17.6

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Create a nuxt project
2. add @sentry/nuxt
3. Lock vue version on 3.5.13 to prevent memory leak in useFetch
4. Notice that error is displayed on build.

Expected Result

I expect sentry to work on this non broken version of vue.

Actual Result

Additional Context

Here is a link to the issue on nuxt with the memory leak preventing us from using the required vue version. nuxt/nuxt#32240

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-935 @sentry/nuxt is not working with nuxt + locked vue@3.5.13 (because of memory leak in 3.5.17)

[Lms24]

Hey @SebbeJohansson thanks for writing in! I'm not sure how the Sentry SDK would cause this installation error. We do have peer dependencies declared but in very liberal ranges, especially for vue (2.x || 3.x). See:

• sentry-nuxt
• sentry-vue

In the screenshot, I don't see any mentioning of Sentry either. Not saying this isn't a bug just that it seems like we're lacking some information. Just to confirm: Have you tried removing node_modules and your lock file?

[SebbeJohansson]

Hi. The issue appeared when we added Sentry to our production enviroment, which is why we thought it was due to this. It seems like it was due to other issues.

Thanks for responding!