[harlan-zw]

🔗 Linked issue

resolves #365

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Combined dependency update from the dependency-updates routine (issue #365). All 22 outdated catalog entries move to their latest versions: Nuxt stack to 4.6.2, UnoCSS to 66.11.0, Vitest 5.0.5, Vue 3.5.44, vue-router 5.4.0, ESLint 10.13.0, and the dev catalog (@nuxt/content 3.16.2, @nuxt/test-utils 4.3.4, playwright-core 1.64.1, execa 10.2.0, @harlan-zw/comark-content 0.2.2, iconify sets).

Two majors are included:

• happy-dom 20 → 21. No code change needed; @nuxt/test-utils 4.3.4 declares a happy-dom >=20.0.11 peer, so 21.0.3 satisfies it.
• nuxtseo-layer-devtools 5 → 6. Checked the published package before bumping: composables/state.ts and composables/shiki.ts are byte-identical to 5.3.16 and rpc.ts only adds a defensive $router?.afterEach check, so the devtools client needs no migration.

@nuxt/devtools-kit moves to 4.0.0-beta.5, keeping the exact-pin beta channel style. @nuxt/devtools-ui-kit has newer betas published but was not in this run's update evidence, so it stays on 4.0.0-beta.4; a reviewer should say if the two should move in lockstep.

TypeScript stays on 6.0.3 and every consumer keeps its catalog: reference. pnpm also pruned the stale minimumReleaseAgeExclude pins (nuxt@4.6.0, @nuxt/kit@4.6.0, @harlan-zw/comark-content@0.2.0) while regenerating the lockfile, which minimumReleaseAgeExcludePrune: true asks for.

One heads-up for local runs: with a stubbed module build (nuxt-module-build build --stub), the content-v3 e2e fixture fails with Top-level await is not available in the configured target environment ("es2019") because the stub's jiti shim gets inlined into a client chunk. A real nuxt-module-build build clears it. Unrelated to these versions, but easy to misread as a regression.

🤖 AI disclosure: Harlan Agent Kit modified this description. My AI open-source policy.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@nuxtjs/robots@366

commit: c483156

[github-actions]

Nuxt Module Size Analyzer

Runtime size changed.

Module	Client gzip	Server raw
@nuxtjs/robots	624 B 🔴 +16 B (+2.6%)	165 kB 🔴 +469 B (+0.3%)

Package files (6)

Rows overlap and include unused code. These totals do not measure deployed output or npm downloads.
Excludes dependency files, types, source maps, and other non-code files.

Package files	Summed gzip	Raw	Δ gzip
@nuxtjs/robots · export .	7.2 kB	27 kB	—
@nuxtjs/robots · export ./content	292 B	503 B	—
@nuxtjs/robots · export ./util	467 B	784 B	—
@nuxtjs/robots · built code files	43 kB	140 kB	—
@nuxtjs/robots · app source files	3.3 kB	7.2 kB	—
@nuxtjs/robots · server source files	9.1 kB	21 kB	—

Dependencies (8)

Declared dependencies. Their installed size does not show runtime cost.

Package	Dependency	Requested
@nuxtjs/robots	@fingerprintjs/botd	catalog:
@nuxtjs/robots	@nuxt/kit	catalog:
@nuxtjs/robots	@vueuse/core	catalog:
@nuxtjs/robots	consola	catalog:
@nuxtjs/robots	defu	catalog:
@nuxtjs/robots	nuxt-site-config	catalog:
@nuxtjs/robots	nuxtseo-shared	catalog:
@nuxtjs/robots	ufo	catalog:

How this is measured

• Compare the same app with and without the module.
• Client: all emitted JS/CSS, summed per-file gzip. This includes lazy chunks.
• Server: deployed files, including external dependencies. Source maps are excluded.
• Default module settings, Node server preset. Memory and request speed are outside this report.

_{Base: main @ f9b1ec6 · 2026-10-14 · differences below 16 B are ignored}

[harlan-zw]

🤖 BLOCKED

Harlan Agent Kit posted this automated review. It is not Harlan's personal review or approval. AI open source policy. A person still decides the merge.

• Merge gate: Passed.

• Review gate: Passed. No finding above 80/100.

• CI gate: BLOCKED. ci / test failed.

• Logged (12/100): The release-age exclusion list still pins @nuxt/devtools-kit@4.0.0-beta.4 after the dependency was bumped to 4.0.0-beta.5, leaving dead bookkeeping and no exemption for the version actually installed. View code Optional follow-up: Optional follow-up: prune '@nuxt/devtools-kit@4.0.0-beta.4' (and audit '@nuxt/devtools@4.0.0-beta.4' the same way) or repin the exclusion to 4.0.0-beta.5, and consider extending the dependency-update routine to rewrite these pins when exact-pin betas move.

  • Ask an agent to verify and fix this finding

• Logged (10/100): devtools-kit moved to 4.0.0-beta.5 while the deprecated devtools-ui-kit stays on 4.0.0-beta.4, skewing the two beta-channel packages the devtools app is built from. View code Optional follow-up: Optional follow-up: evaluate moving @nuxt/devtools-ui-kit to the matching newer beta in lockstep with devtools-kit, or document why the deprecated ui-kit beta.4 is intentionally retained.

  • Ask an agent to verify and fix this finding

• Open (100/100): Required check "ci / test" fails on the pull request head commit. View code Next: This pull request needs Approval before the controller publishes a repair.

Selected findings run after merge and open separate pull requests.