fix(deps): Upgrade to nuxt 4.5.1 [security]. - #210
Merged
Conversation
Carries the nuxt security fix. Supersedes #183 (which pins 4.4.7). Two resolution overrides keep the dependency graph single-copy, which nuxt 4.5 requires: - `vite ^8`: nuxt 4.5 builds on the rolldown-based vite 8 while vitest still resolves a vite 7. Transforming through two vite majors throws `Missing field moduleType` and no test file starts its pool worker. - `vue ^3.5.40`: nuxt's nested vue outranked the hoisted 3.5.28, so nitro traced one copy while the renderer imported the other and the server bundle shipped an incomplete `vue` — every SSR route 500'd with `Cannot find module .output/server/node_modules/vue/index.mjs`. vue-component-meta stays at 3.2.9; its 3.3 upgrade is a separate PR.
drubot
force-pushed
the
feature/nuxt-4.5-upgrade
branch
from
August 3, 2026 20:34
240cd65 to
3c36edd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Carries the nuxt security fix and supersedes #183 (which pins 4.4.7). Follows #208 (vitest 4 + @nuxt/test-utils 4), now merged — this PR is rebased on
1.xand contains only the nuxt bump.Changes
nuxt/@nuxt/kit/@nuxt/schema: 4.2.1 → 4.5.1, plus two resolution overrides that keep the graph single-copy — nuxt 4.5 needs both:vite ^8— nuxt 4.5 builds on the rolldown-based vite 8 while vitest still resolves a vite 7. Transforming through two vite majors throwsMissing field moduleTypeand no test file starts its pool worker.vue ^3.5.40— nuxt's nested vue outranked the hoisted 3.5.28, so nitro traced one copy while the renderer imported the other. The server bundle shipped an incompletevue, and every SSR route 500'd withCannot find module .output/server/node_modules/vue/index.mjs.vue-component-metadeliberately stays at 3.2.9 — its 3.3 upgrade breaksincludePackagesand is a separate PR.Verification
CI green on this branch (run): lint pass, unit 7/7 files, e2e 5/5 files (dev + production servers, real browser). Locally: unit 128/128, e2e 24/24.
Follow-ups
vue-component-meta3.3 upgrade🤖 Generated with Claude Code
https://claude.ai/code/session_0135TzeJ5xX7vdwouF9Qd6yv