deps(deps): bump nuxt from 4.3.1 to 4.4.5#12
Merged
Conversation
Bumps [nuxt](https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt) from 4.3.1 to 4.4.5. - [Release notes](https://github.com/nuxt/nuxt/releases) - [Commits](https://github.com/nuxt/nuxt/commits/v4.4.5/packages/nuxt) --- updated-dependencies: - dependency-name: nuxt dependency-version: 4.4.5 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Nuxt 4.4.5 bump (#12) を CI が通る状態に仕上げる。3 つの修正: 1. tsconfig.json: project references 形式へ移行 Nuxt 4.4 は .nuxt/tsconfig.json を per-context な 4 ファイル (app / server / shared / node) に分割した。単一 extends 形式では 解決不能になるため、references を 4 つ並べる公式書式に変更。 ref: https://nuxt.com/docs/4.x/getting-started/upgrade#typescript-configuration-splitting 2. @nuxt/schema を 4.4.5 で明示 pin @nuxt/[email protected] の peer dep "@nuxt/schema": "^4.4.2" の影響で bun が 旧 4.4.2 を top-level に hoist していた。4.4.2 dist は DefineNuxtConfig 型を export しないため、nuxt/config の型チェーン (interface DefineNuxtConfig extends _DefineNuxtConfig<NuxtConfig>) が call signature を失い "DefineNuxtConfig has no call signatures" で tsc が fail していた。 package.json に exact pin することで lockfile を 4.4.5 に強制し解決。 ref: nuxt/nuxt#20221 3. CI Type check: tsc --noEmit → tsc -b project references 形式は -b (build mode) で walk する必要がある。 Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
1 task
risingore
added a commit
that referenced
this pull request
May 16, 2026
kima-core/docs/guides/nuxt-version-bumps.md を sync-to-derivatives.sh の NUXT_TEMPLATES 限定配布リストに加え、Nuxt 系派生 (kireiphoto / nuxt-cloudflare-template) に配布した結果。 内容は PR #12 で初めて顕在化した Nuxt 4.4 の 3 罠 (tsconfig split / @nuxt/schema peer hoist / @types/node 不採用) の運用手順と チェックリスト。将来 Nuxt の minor/major bump dependabot PR を扱う際の 事前読み込み資料。 Co-authored-by: risingore <[email protected]> Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
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
1 participant
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.
Bumps nuxt from 4.3.1 to 4.4.5.
Release notes
Sourced from nuxt's releases.
Commits
08f34b5v4.4.5adc9ebffix(nuxt): explicitly freeze head during island plugin phase (#35010)16fde3afix(nuxt): defer head DOM updates until page transition finishes (#35016)d01928efix(nuxt): correct island transform for server pages and 'deep' mode (#35005)151f918fix(nuxt): handle string presets in auto-imports (#35013)d1f7c8afix(nuxt): respect factory fetch/baseURL options in serveruseFetch(#35003)ddbd34dfix(nuxt): dedupegetCachedDatafor concurrent callers sharing a key (#34999)61dcde4fix(nuxt): cast partial nitro handlers when prepending to server arrays9974078fix(nitro): preserveserverHandlersarray afternitro:config(#34985)887628efix(nuxt): only force suspense remount after first resolve (#34949)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)