feat(devtools): drive Vite DevTools through the devtools config option on Vite 8.3+

[antfubot]

🔗 Linked issue

📚 Description

Vite 8.3 registers the Vite DevTools integration itself from the top-level devtools config option (vitejs/vite#23333). This PR detects the running Vite version:

• Vite ≥ 8.3 — Nuxt DevTools no longer installs the DevTools() plugin manually. It seeds the Vite devtools config option (branding, and clientAuth for disableAuthorization) and lets Vite core load the integration. This puts the toggle in user hands: vite: { devtools: false } in nuxt.config turns Vite DevTools off, and user-provided devtools config keys win over our defaults.
• Vite < 8.3 — falls back to lazily importing @vitejs/devtools and registering the DevTools() plugin, as before.

Verified against playgrounds-ecosystem/:

• nuxt5 (Nuxt 5 nightly, now pinned to Vite 8.3 via override): hub mounted at /__devtools/ with Nuxt branding in __connection.json, dock (devframes-dock-embedded) renders in the browser, Nuxt client served at /__nuxt_devtools__/client/; with vite: { devtools: false } the hub is not mounted. build + typecheck pass.
• nuxt4 (Nuxt 4.5.1 / Vite 8.1.5): manual-plugin fallback still mounts the hub with Nuxt branding and the dock renders. build + typecheck pass.

Also documents the new toggle in the v4 migration guide.

---

This PR was created with the help of an agent.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​unocss/​preset-uno@​66.10.1 ⏵ 66.10.2				+1
	@​unocss/​eslint-config@​66.10.1 ⏵ 66.10.2				+1
	@​unocss/​nuxt@​66.10.1 ⏵ 66.10.2				+1
	@​unocss/​preset-attributify@​66.10.1 ⏵ 66.10.2				+1
	@​devframes/​hub@​0.9.12 ⏵ 0.9.19	+1		+1	+1
	@​unocss/​preset-icons@​66.10.1 ⏵ 66.10.2				+1
	@​unocss/​core@​66.10.1 ⏵ 66.10.2
	@​unocss/​reset@​66.10.1 ⏵ 66.10.2	+1			+1
	@​iconify-json/​simple-icons@​1.2.95 ⏵ 1.2.96				+1
	@​unocss/​preset-mini@​66.10.1 ⏵ 66.10.2				+1
	@​iconify-json/​carbon@​1.2.26 ⏵ 1.2.27			+1	+1
	@​types/​node@​26.5.1
	floating-vue@​5.2.2 ⏵ 5.4.0	+1		+1	+7
	vite@​8.2.2 ⏵ 8.3.0	+1		+1
	devframe@​0.9.12 ⏵ 0.9.19			+1	+1
	nuxt-nightly@​5.0.0-29812228.98bec0f7 ⏵ 5.0.0-29819633.9319fd64	-4		+1
	cronstrue@​3.24.0 ⏵ 3.26.0				-3
	@​devframes/​plugin-code-server@​0.9.12 ⏵ 0.9.19	+1			+1
	magicast@​0.5.5
	@​devframes/​plugin-data-inspector@​0.9.12 ⏵ 0.9.19	+1			+1
	knip@​6.34.0 ⏵ 6.35.1
	unocss@​66.10.1 ⏵ 66.10.2
	unimport@​7.0.1 ⏵ 7.0.2				+1

View full report

[cloudflare-workers-and-pages]

Deploying nuxt-devtools with    Cloudflare Pages

Latest commit:	2893b48
Status:	✅  Deploy successful!
Preview URL:	https://be8afd28.nuxt-devtools.pages.dev
Branch Preview URL:	https://feat-vite-devtools-config-in.nuxt-devtools.pages.dev

View logs

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 96d963f1-b0a6-47c1-8266-8f86f10000f3

📥 Commits

Reviewing files that changed from the base of the PR and between 64376ec and 2893b48.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• package.json
• pnpm-workspace.yaml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The module now detects the Vite version and configures DevTools through Vite’s top-level devtools option for Vite 8.3 and later. It preserves manual plugin registration for older versions. A helper handles disabled, missing, and boolean devtools settings. Authorization and branding use the shared configuration path. Migration documentation and the Nuxt 5 playground cover the version-specific behavior.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 2893b

No concrete current-head issue remains that should block merging.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (2 skipped: 2…	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: configuring Vite DevTools through the devtools option for Vite 8.3 and newer.
Description check	✅ Passed	The description directly explains the Vite 8.3 integration, the older-version fallback, the new disable option, documentation changes, and verification results.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/vite-devtools-config-integration

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}