fix(vue): support for vue-router v5

[penglezos]

Description

Currently, @vercel/analytics (v1.6.1) specifies vue-router@^4 as an optional peer dependency.
With the release of vue-router v5, projects using the latest version of Vue encounter ERRESOLVE errors during installation because of this version mismatch.

Console output

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vercel/analytics@1.6.1
npm error Found: vue-router@5.0.2
npm error node_modules/vue-router
npm error   vue-router@"^5.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vue-router@"^4" from @vercel/analytics@1.6.1
npm error node_modules/@vercel/analytics
npm error   @vercel/analytics@"^1.6.1" from the root project
npm error
npm error Conflicting peer dependency: vue-router@4.6.4
npm error node_modules/vue-router
npm error   peerOptional vue-router@"^4" from @vercel/analytics@1.6.1
npm error   node_modules/@vercel/analytics
npm error     @vercel/analytics@"^1.6.1" from the root project

Changes

This PR updates the package and peerDependencies to support vue-router v5.

[vercel]

@penglezos is attempting to deploy a commit to the Analytics Test Projects Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​remix-run/​serve@​2.13.1 ⏵ 2.17.4				+4
	@​remix-run/​node@​2.14.0 ⏵ 2.17.4		+75	+3	+2
	@​sveltejs/​adapter-vercel@​6.2.0 ⏵ 6.3.1	+1		+1	-2
	@​remix-run/​react@​2.14.0 ⏵ 2.17.4	-1	+22	+2	+2
	@​remix-run/​dev@​2.13.1 ⏵ 2.17.4			+1	+5
	@​sveltejs/​kit@​2.49.1 ⏵ 2.50.1		+22		-1
	vite@​7.2.7 ⏵ 7.3.1			+1
	svelte@​5.45.5 ⏵ 5.49.1	-5		+1
	vue@​3.5.25 ⏵ 3.5.27	+1			+1
	svelte-check@​4.0.5 ⏵ 4.3.6	+1			+3
	vue-router@​5.0.2
	@​vitejs/​plugin-vue@​6.0.2 ⏵ 6.0.4	+1			+8

View full report

[penglezos]

Hi! This PR looks all set if everything's okay on your end, can we get this merged?

[ghost]

and you deploy if it will be deployed yes

…

On Mon, Feb 16, 2026 at 2:04 AM Panagiotis Englezos < ***@***.***> wrote: *penglezos* left a comment (vercel/analytics#185) <#185 (comment)> Hi! This PR looks all set if everything's okay on your end, can we get this merged? — Reply to this email directly, view it on GitHub <#185 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B5ZXSWWEJP4YA62UGQF2QOT4MGI4NAVCNFSM6AAAAACTV4TSJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMBXGU2TKNBVGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Oui-Dev]

Will this be merged soon? I'm having conflicts preventing me from updating my stack.

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vercel/analytics@2.0.1
npm error Found: vue-router@5.0.4
npm error node_modules/vue-router
npm error   peerOptional vue-router@"^4.5.0 || ^5.0.0" from @nuxt/ui@4.6.0
npm error   node_modules/@nuxt/ui
npm error     @nuxt/ui@"^4.6.0" from the root project
npm error   vue-router@"^5.0.3" from nuxt@4.4.2
npm error   node_modules/nuxt
npm error     nuxt@"^4.4.2" from the root project
npm error     peer nuxt@"^4.4.2" from @nuxt/nitro-server@4.4.2
npm error     node_modules/@nuxt/nitro-server
npm error       @nuxt/nitro-server@"4.4.2" from nuxt@4.4.2
npm error     3 more (@nuxt/vite-builder, @vercel/analytics, @vercel/speed-insights)
npm error
npm error Could not resolve dependency:
npm error peerOptional vue-router@"^4" from @vercel/analytics@2.0.1
npm error node_modules/@vercel/analytics
npm error   @vercel/analytics@"^2.0.1" from the root project
npm error
npm error Conflicting peer dependency: vue-router@4.6.4
npm error node_modules/vue-router
npm error   peerOptional vue-router@"^4" from @vercel/analytics@2.0.1
npm error   node_modules/@vercel/analytics
npm error     @vercel/analytics@"^2.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.