fix(nuxt): remove the module as breaking change

[HugoRCD]

This reverts commit #104 as the Nuxt module should be a breaking change.

---

I will open another PR for 2.0 with the Nuxt module + runtime usage, the only breaking change will be:

- import { Analytics } from '@vercel/speed-insights/nuxt'
+ import { Analytics } from '@vercel/speed-insights/nuxt/runtime'

But the advantage will be that most people will only have to do:

export default defineNuxtConfig({
  modules: ['@vercel/speed-insights']
})

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
speed-insights-astro	Ready	Preview	Comment	Dec 2, 2025 10:14am
speed-insights-nextjs	Ready	Preview	Comment	Dec 2, 2025 10:14am
speed-insights-nuxt	Ready	Preview	Comment	Dec 2, 2025 10:14am
speed-insights-remix	Ready	Preview	Comment	Dec 2, 2025 10:14am
speed-insights-sveltekit	Ready	Preview	Comment	Dec 2, 2025 10:14am
speed-insights-vue	Ready	Preview	Comment	Dec 2, 2025 10:14am

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	nuxt@​4.2.0 ⏵ 3.9.1	+1	-75		+3
	@​types/​react-dom@​18.2.7 ⏵ 18.2.18	+1		+1	+1
	@​remix-run/​react@​2.14.0
	@​sveltejs/​kit@​2.8.1
	postcss@​8.4.38 ⏵ 8.4.47	+1		+1
	react@​18.2.0
	svelte@​5.0.0
	vue-router@​4.6.3 ⏵ 4.2.5	+5		-1
	vue-router@​4.6.3 ⏵ 4.4.5	+5
	typescript@​5.3.3
	vue@​3.5.25 ⏵ 3.4.14	+1			+2
	react-dom@​18.2.0
	vue@​3.5.25 ⏵ 3.5.13	+1			+2
	@​nuxt/​devtools@​2.7.0 ⏵ 3.1.1	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Critical CVE: Nuxt vulnerable to remote code execution via the browser when running the test locally CVE: GHSA-v784-fjjh-f8r4 Nuxt vulnerable to remote code execution via the browser when running the test locally (CRITICAL) Affected versions: >= 3.4.0 < 3.12.4 Patched version: 3.12.4 From: apps/nuxt/package.json → npm/nuxt@3.9.1 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/nuxt@3.9.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: Uncontrolled resource consumption in npm braces CVE: GHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in braces (HIGH) Affected versions: < 3.0.3 Patched version: 3.0.3 From: pnpm-lock.yaml → npm/lint-staged@14.0.1 → npm/@vercel/style-guide@5.1.0 → npm/nuxt@3.9.1 → npm/astro@4.1.2 → npm/@astrojs/check@0.5.4 → npm/tailwindcss@3.4.4 → npm/braces@3.0.2 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/braces@3.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: Regular Expression Denial of Service (ReDoS) in npm cross-spawn CVE: GHSA-3xgq-45jj-v275 Regular Expression Denial of Service (ReDoS) in cross-spawn (HIGH) Affected versions: >= 7.0.0 < 7.0.5; < 6.0.6 Patched version: 7.0.5 From: pnpm-lock.yaml → npm/lint-staged@14.0.1 → npm/@vercel/style-guide@5.1.0 → npm/nuxt@3.9.1 → npm/astro@4.1.2 → npm/@nuxt/devtools@3.1.1 → npm/cross-spawn@7.0.3 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cross-spawn@7.0.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm glob CLI: Command injection via -c/--cmd executes matches with shell:true CVE: GHSA-5j98-mcp5-4vw2 glob CLI: Command injection via -c/--cmd executes matches with shell:true (HIGH) Affected versions: >= 11.0.0 < 11.1.0; >= 10.2.0 < 10.5.0 Patched version: 10.5.0 From: pnpm-lock.yaml → npm/tailwindcss@3.4.4 → npm/tsup@8.3.5 → npm/@remix-run/dev@2.17.2 → npm/glob@10.4.5 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@10.4.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm node-forge has ASN.1 Unbounded Recursion CVE: GHSA-554w-wpv2-vw27 node-forge has ASN.1 Unbounded Recursion (HIGH) Affected versions: < 1.3.2 Patched version: 1.3.2 From: pnpm-lock.yaml → npm/nuxt@3.9.1 → npm/node-forge@1.3.1 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm node-forge has an Interpretation Conflict vulnerability via its ASN.1 Validator Desynchronization CVE: GHSA-5gfm-wpxj-wjgq node-forge has an Interpretation Conflict vulnerability via its ASN.1 Validator Desynchronization (HIGH) Affected versions: < 1.3.2 Patched version: 1.3.2 From: pnpm-lock.yaml → npm/nuxt@3.9.1 → npm/node-forge@1.3.1 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/node-forge@1.3.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: Nuxt allows DOS via cache poisoning with payload rendering response CVE: GHSA-jvhm-gjrh-3h93 Nuxt allows DOS via cache poisoning with payload rendering response (HIGH) Affected versions: >= 3.0.0 < 3.16.0 Patched version: 3.16.0 From: apps/nuxt/package.json → npm/nuxt@3.9.1 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/nuxt@3.9.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: DOM Clobbering Gadget found in npm rollup bundled scripts that leads to XSS CVE: GHSA-gcx4-mw62-g8wm DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS (HIGH) Affected versions: >= 3.0.0 < 3.29.5; >= 4.0.0 < 4.22.4; < 2.79.2 Patched version: 3.29.5 From: apps/vue/package.json → npm/vite@4.4.11 → npm/rollup@3.28.1 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@3.28.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: DOM Clobbering Gadget found in npm rollup bundled scripts that leads to XSS CVE: GHSA-gcx4-mw62-g8wm DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS (HIGH) Affected versions: >= 3.0.0 < 3.29.5; >= 4.0.0 < 4.22.4; < 2.79.2 Patched version: 4.22.4 From: pnpm-lock.yaml → npm/nuxt@3.9.1 → npm/astro@4.1.2 → npm/rollup@4.7.0 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rollup@4.7.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball CVE: GHSA-vj76-c3g6-qr5v tar-fs has a symlink validation bypass if destination directory is predictable with a specific tarball (HIGH) Affected versions: >= 3.0.0 < 3.1.1; >= 2.0.0 < 2.1.4; < 1.16.6 Patched version: 3.1.1 From: pnpm-lock.yaml → npm/tar-fs@3.0.4 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar-fs@3.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm tar-fs Vulnerable to Link Following and Path Traversal via Extracting a Crafted tar File CVE: GHSA-pq67-2wwv-3xjx tar-fs Vulnerable to Link Following and Path Traversal via Extracting a Crafted tar File (HIGH) Affected versions: < 1.16.4; >= 2.0.0 < 2.1.2; >= 3.0.0 < 3.0.7 Patched version: 3.0.7 From: pnpm-lock.yaml → npm/tar-fs@3.0.4 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar-fs@3.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		High CVE: npm tar-fs can extract outside the specified dir with a specific tarball CVE: GHSA-8cj5-5rvv-wf4v tar-fs can extract outside the specified dir with a specific tarball (HIGH) Affected versions: < 1.16.5; >= 2.0.0 < 2.1.3; >= 3.0.0 < 3.0.9 Patched version: 3.0.9 From: pnpm-lock.yaml → npm/tar-fs@3.0.4 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar-fs@3.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[feugy]

Could you change the version number in packages/web/package.json to 1.3.1 please?
So I won't need a new PR to release this package.

CI and deployments are failing because of an outdated pnpm-lock.json file. Try running pnpm i please.

[HugoRCD]

@feugy Done

[vercel]

Additional Suggestion:

The README shows the wrong import path. It imports from '@vercel/speed-insights/vue' but should import from '@vercel/speed-insights/nuxt' to match the actual code in the app.

View Details

📝 Patch Details

diff --git a/apps/nuxt/README.md b/apps/nuxt/README.md
index 6890059..9e597c3 100644
--- a/apps/nuxt/README.md
+++ b/apps/nuxt/README.md
@@ -16,7 +16,7 @@ We also imported and used `<SpeedInsights />` component in `layouts/default.vue`
 
 ```vue
 <script setup>
-import { SpeedInsights } from '@vercel/speed-insights/vue';
+import { SpeedInsights } from '@vercel/speed-insights/nuxt';
 </script>
 
 <template>

Analysis

Incorrect import path in Nuxt README causes wrong telemetry framework reporting

What fails: The apps/nuxt/README.md shows an example importing SpeedInsights from '@vercel/speed-insights/vue' instead of '@vercel/speed-insights/nuxt', causing the Speed Insights component to report the wrong framework in telemetry.

How to reproduce:

1. Follow the README example in apps/nuxt/README.md (line 19)
2. Use import { SpeedInsights } from '@vercel/speed-insights/vue'
3. Check the telemetry data sent to Vercel - it will report framework: 'vue'

Result: Telemetry incorrectly identifies the framework as Vue instead of Nuxt

Expected: Should import from '@vercel/speed-insights/nuxt' to match the actual implementation in apps/nuxt/layouts/default.vue (line 2) and correctly report framework: 'nuxt' in telemetry. Both imports are valid exports (per packages/web/package.json exports), but they produce different telemetry results - the Nuxt version passes framework: 'nuxt' while the Vue version passes framework: 'vue' to the Speed Insights service.

[feugy]

Thank you!