[yamcodes]

Summary

Bumps the pinned Vite devDependency from 8.0.10 to 8.0.16 across the workspace, playgrounds, docs site, dashboard, and examples. Lockfiles (nub.lock and the affected example package-lock.json files) follow that pin, including Vite’s updated Rolldown 1.0.3 tree.

@arkenv/vite-plugin still peers vite as ^4 || ^5 || ^6 || ^7 || ^8. No changeset: this is a devDependency pin, not a published API change.

Nuxt continues to resolve its own Vite 8.3.0. Vitest’s optional peer at the repo root stays locked at 8.0.10 because the root package does not depend on Vite directly.

Test plan

• nub install --frozen-lockfile
• nub run sync:examples:check
• @arkenv/vite-plugin Vitest: 2 files, 23 tests passed against the installed Vite 8.0.16

  

[changeset-bot]

⚠️ No Changeset found

Latest commit: 37d8606

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@arkenv/agent-plugin

npm i https://pkg.pr.new/@arkenv/agent-plugin@2062

arkenv

npm i https://pkg.pr.new/arkenv@2062

@arkenv/build

npm i https://pkg.pr.new/@arkenv/build@2062

@arkenv/bun-plugin

npm i https://pkg.pr.new/@arkenv/bun-plugin@2062

@arkenv/core

npm i https://pkg.pr.new/@arkenv/core@2062

@arkenv/fumadocs-ui

npm i https://pkg.pr.new/@arkenv/fumadocs-ui@2062

@arkenv/nextjs

npm i https://pkg.pr.new/@arkenv/nextjs@2062

@arkenv/nuxt

npm i https://pkg.pr.new/@arkenv/nuxt@2062

@arkenv/rsbuild-plugin

npm i https://pkg.pr.new/@arkenv/rsbuild-plugin@2062

@arkenv/standard

npm i https://pkg.pr.new/@arkenv/standard@2062

@arkenv/tanstack-addon

npm i https://pkg.pr.new/@arkenv/tanstack-addon@2062

@arkenv/vite-plugin

npm i https://pkg.pr.new/@arkenv/vite-plugin@2062

commit: 37d8606

[arkenv-bot]

📦 Bundle Size Report

Package	Size	Limit	Diff	Status
@arkenv/vite-plugin	1.46 kB	7.81 kB	0.0%	✅

✅ All size limits passed!

[pullfrog]

✅ No new issues found.

Reviewed changes — full 17-file diff for the vite 8.0.10 → 8.0.16 pin bump and its lockfile regeneration.

• Workspace pins raised to 8.0.16 — the pinned vite devDependency is bumped consistently across apps/dash, apps/www, apps/playgrounds/{arkenv-cli,solid-start,tanstack-start,vite,vite-legacy}, packages/vite-plugin, and examples/{with-solid-start,with-tanstack-start,with-vite-react,with-vite-react-zod}. No tracked package.json retains 8.0.10.
• @arkenv/vite-plugin peer range untouched — still ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 at packages/vite-plugin/package.json:35, so 8.0.16 stays inside ^8. A devDependency pin with no published API change correctly carries no changeset.
• Lockfiles regenerated — nub.lock plus the four affected example package-lock.json files follow the pin, including Vite 8.0.16's refreshed transitive tree (rolldown 1.0.0-rc.17 → 1.0.3, @vitejs/devtools ^0.1.0 → ^0.1.18, postcss/tinyglobby) and incidental example-only transitive refreshes. The remaining [email protected] snapshot keys in nub.lock are resolver co-existence (Nuxt's own [email protected], Vitest's optional root peer), consistent with the PR description — not stale leftovers.

No behavioral surface: version strings and generated lockfile trees only. Reported verification (nub install --frozen-lockfile, sync:examples:check, vite-plugin Vitest 23 tests) covers the affected paths.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}