[Vue Router warn]: The `next()` callback in navigation guards is deprecated. Return the value instead of calling `next(value)`.

[mrleblanc101]

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?

Self-hosted/on-premise

Which SDK are you using?

@sentry/nuxt

SDK Version

10.40.0

Framework Version

4.3.1

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

Upgrade to Vue-router 5.0.0 in your nuxt project

Expected Result

No console warning

Actual Result

http://localhost:3000/_nuxt/@fs/Users/sleblanc/www/project_name/nuxt4/node_modules/.pnpm/@sentry+vue@10.40.0_pinia@3.0.4_typescript@5.9.3_vue@3.5.29_typescript@5.9.3___vue@3.5.29_typescript@5.9.3_/node_modules/@sentry/vue/src/router.ts

[Vue Router warn]: The next() callback in navigation guards is deprecated. Return the value instead of calling next(value).

Additional Context

sentry-javascript/packages/vue/src/router.ts

Lines 119 to 124 in 89b437f

	// Vue Router 4 no longer exposes the `next` function, so we need to
	// check if it's available before calling it.
	// `next` needs to be called in Vue Router 3 so that the hook is resolved.
	if (next) {
	next();
	}

Priority

_{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-1811

[logaretm]

Thanks for reporting this, there is a PR already for this:

#19476

We can create PR and accelerate a fix for this instead on waiting for this PR

[mrleblanc101]

@logaretm I would've opened a PR if I knew how to fix the problem 😛
Good to know that someone already opened a PR.
I couldn't find any issue mentioning this problem when I did a quick search (but github search is pretty bad for matching an exact error message), so how could I know a PR already fixed an issue that wasn't even opened yet ? 😉

[logaretm]

Totally fair, I'm just pointing out that it is in progress. I guess now we do have an issue to link it to, no? 😄

I will take a look at it tomorrow and see if we can ship it ASAP.