void 0.7.12 → 0.7.13

package/AGENT_PROMPT.md

@@ -1,6 +1,6 @@
 ## Void
 
-This project uses [Void](https://void.cloud) — a fullstack Vite plugin + deployment platform for Cloudflare. `voidPlugin()` in `vite.config.ts` gives you file-based API routing on Hono (`routes/`), Inertia-inspired server-rendered pages with co-located loaders/actions (`pages/` + `@void/vue` or `@void/react`), auto-provisioned D1/KV/R2 bindings, first-class Drizzle ORM integration (schema in `db/schema.ts` -> `void/db` Drizzle instance -> typed routes -> typed fetch client), built-in auth, queues, cron jobs, edge caching (ISR), and one-command deploys via `npx void deploy`. For first-time setup, prefer `npx void init`; in an empty directory, install `void` first and let the interactive flow scaffold the starter, add the matching framework adapter, configure project files, handle auth, and link or create the deploy project before the first deploy. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. Use `void` and `@void/*` package names in source code and package manifests.
+This project uses [Void](https://void.cloud) — a fullstack Vite plugin + deployment platform for Cloudflare. `voidPlugin()` in `vite.config.ts` gives you file-based API routing on Hono (`routes/`), Inertia-inspired server-rendered pages with co-located loaders/actions (`pages/` + `@void/vue` or `@void/react`), auto-provisioned D1/KV/R2 bindings, first-class Drizzle ORM integration (schema in `db/schema.ts` -> `void/db` Drizzle instance -> typed routes -> typed fetch client), built-in auth, queues, cron jobs, edge caching (ISR), and one-command deploys via `npx void deploy`. For first-time setup, prefer `npx void init`; in an empty directory, install `void` first and let the interactive flow scaffold the starter with Vite+ by default, add the matching framework adapter, configure project files, handle auth, and link or create the deploy project before the first deploy. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. Use `void` and `@void/*` package names in source code and package manifests.
 
 Database: define Drizzle tables in `db/schema.ts`, import `db` from `void/db` and tables from `@schema`. Use `void db push` for prototyping, `void db generate` for production migrations. `drizzle-orm` and `drizzle-kit` ship with void (no extra install). Migrations live in `db/migrations/`.
 

package/README.md

@@ -21,7 +21,7 @@ Install the Void CLI:
 npm install -D void
 ```
 
-If you run `void init` in an empty directory, the scaffold flow adds the matching Pages adapter and Vite dependencies for you.
+If you run `void init` in an empty directory, the scaffold flow adds the matching Pages adapter and Vite+ by default.
 
 Then run `npx void init`. In an empty directory, the full interactive flow can scaffold a starter, configure local project files, log you in, and link or create your Void project so the next step is just `npx void deploy`. In an existing app, it configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`.
 
@@ -82,7 +82,7 @@ There is Vinext-specific source in the repo, but it is intentionally on hold and
 
 ## Documentation
 
-Full docs live at [void.cloud/docs](https://void.cloud/docs).
+Full docs live at [void.cloud/guide](https://void.cloud/guide).
 
 ## License
 

package/dist/cli/cli.mjs

@@ -1539,7 +1539,7 @@ else if (command === "prepare") {
 	});
 } else if (command === "init") {
 	const root = process.cwd();
-	import("../init-iIiQWzyB.mjs").then(({ runInitCommand, parseInitArgs }) => {
+	import("../init-Br5DTaG7.mjs").then(({ runInitCommand, parseInitArgs }) => {
 		let initArgs;
 		try {
 			initArgs = parseInitArgs(args.slice(1));
@@ -1628,7 +1628,7 @@ else if (command === "-v" || command === "--version") {
 		const root = process.cwd();
 		switch (cmd) {
 			case "init": {
-				const { runInitCommand, parseInitArgs } = await import("../init-iIiQWzyB.mjs");
+				const { runInitCommand, parseInitArgs } = await import("../init-Br5DTaG7.mjs");
 				await runInitCommand(root, parseInitArgs([]));
 				return;
 			}

package/dist/{init-iIiQWzyB.mjs → init-Br5DTaG7.mjs}

@@ -1,7 +1,7 @@
 import { a as join, i as isAbsolute, n as dirname, o as relative, s as resolve, t as basename } from "./pathe.M-eThtNZ-D-kmWkCS.mjs";
 import { n as cliTitle } from "./output-D3g5otMC.mjs";
 import { c as getToken, n as PlatformClient, u as isStagingMode } from "./client-C_DYiXeu.mjs";
-import { _ as me, c as R, g as ge, i as Ee, u as Se, v as ue, x as q, y as ye } from "./dist-D2L3_KTK.mjs";
+import { _ as me, c as R, g as ge, i as Ee, l as Re, u as Se, v as ue, x as q, y as ye } from "./dist-D2L3_KTK.mjs";
 import { a as writeProjectConfig, r as readProjectConfig } from "./project-DhB4A8_g.mjs";
 import { c as getDatabaseDialect, f as readConfig } from "./config-CeRQg3Lz.mjs";
 import { r as detectFramework } from "./plugin-inference-BexV6LL3.mjs";
@@ -208,6 +208,16 @@ const SCAFFOLD_BASE_DEV_DEPENDENCIES = {
 	vite: "^8.0.10",
 	typescript: "^5.9.3"
 };
+const SCAFFOLD_VITE_PLUS_DEV_DEPENDENCIES = { "vite-plus": "^0.1.21" };
+const SCAFFOLD_TOOLCHAIN_OPTIONS = [{
+	value: "vite-plus",
+	label: "Vite+",
+	hint: "Uses the Vite+ toolchain and vp commands."
+}, {
+	value: "vite",
+	label: "Vite",
+	hint: "Uses plain Vite commands without Vite+."
+}];
 const REACT_SCAFFOLD_COMPILER_DEV_DEPENDENCIES = {
 	"@rolldown/plugin-babel": "^0.2.3",
 	"@vitejs/plugin-react": "^6.0.1",
@@ -294,7 +304,7 @@ function getScaffoldTsconfigCompilerOptions(framework) {
 	return framework ? { ...SCAFFOLD_FRAMEWORKS[framework].tsconfigCompilerOptions } : {};
 }
 function createPagesStarterTemplate(options) {
-	const { framework, starterMode, voidPackageSpec, adapterPackageSpec } = options;
+	const { framework, starterMode, toolchain = "vite", voidPackageSpec, adapterPackageSpec } = options;
 	const config = SCAFFOLD_FRAMEWORKS[framework];
 	const files = {
 		"vite.config.ts": getViteConfig(framework, config),
@@ -308,9 +318,9 @@ function createPagesStarterTemplate(options) {
 	}
 	return {
 		scripts: {
-			dev: "vite",
-			build: "vite build",
-			preview: "vite preview"
+			dev: toolchain === "vite-plus" ? "vp dev" : "vite",
+			build: toolchain === "vite-plus" ? "vp build" : "vite build",
+			preview: toolchain === "vite-plus" ? "vp preview" : "vite preview"
 		},
 		dependencies: {
 			...SCAFFOLD_BASE_DEPENDENCIES,
@@ -319,6 +329,7 @@ function createPagesStarterTemplate(options) {
 		devDependencies: {
 			void: voidPackageSpec,
 			...SCAFFOLD_BASE_DEV_DEPENDENCIES,
+			...toolchain === "vite-plus" ? SCAFFOLD_VITE_PLUS_DEV_DEPENDENCIES : {},
 			[config.adapterPackage]: adapterPackageSpec,
 			...config.devDependencies
 		},
@@ -823,6 +834,53 @@ function isScaffoldableEmptyProject(root) {
 	if (Object.keys(scripts).some((name) => name !== "test")) return false;
 	return true;
 }
+function shouldPromptForInitLocation(root) {
+	if (isScaffoldableEmptyProject(root)) return false;
+	if (existsSync(join(root, "package.json"))) return false;
+	if (existsSync(join(root, VOID_CONFIG_FILE))) return false;
+	return findViteConfig(root) === void 0;
+}
+function validateSubfolderName(root, value) {
+	const name = value?.trim() ?? "";
+	if (!name) return "Enter a folder name.";
+	if (name === "." || name === ".." || name.includes("/") || name.includes("\\")) return "Enter a single folder name, not a path.";
+	if (existsSync(join(root, name))) return "That folder already exists.";
+}
+async function resolveInitRoot(root) {
+	if (!shouldPromptForInitLocation(root)) return root;
+	const choice = await Ee({
+		message: "This folder is not empty. Where should Void initialize?",
+		initialValue: "subfolder",
+		options: [{
+			value: "subfolder",
+			label: "Create a new subfolder",
+			hint: "Scaffold a new app inside this directory."
+		}, {
+			value: "current",
+			label: "Continue here",
+			hint: "Add package.json, vite.config.ts, and Void files to this directory."
+		}]
+	});
+	if (q(choice)) {
+		me("Setup cancelled.");
+		process.exit(0);
+	}
+	if (choice === "current") return root;
+	const folder = await Re({
+		message: "New project folder name:",
+		placeholder: "my-void-app",
+		initialValue: "my-void-app",
+		validate: (value) => validateSubfolderName(root, value)
+	});
+	if (q(folder)) {
+		me("Setup cancelled.");
+		process.exit(0);
+	}
+	const nextRoot = join(root, folder.trim());
+	mkdirSync(nextRoot, { recursive: true });
+	R.info(`Scaffolding in ${nextRoot}`);
+	return nextRoot;
+}
 function parsePackageManagerField(pkg) {
 	if (!pkg || typeof pkg !== "object") return;
 	const raw = pkg.packageManager;
@@ -1566,6 +1624,18 @@ async function promptStarterMode() {
 	}
 	return choice;
 }
+async function promptScaffoldToolchain() {
+	const choice = await Ee({
+		message: "Choose a Pages scaffold toolchain:",
+		initialValue: "vite-plus",
+		options: [...SCAFFOLD_TOOLCHAIN_OPTIONS]
+	});
+	if (q(choice)) {
+		me("Setup cancelled.");
+		process.exit(0);
+	}
+	return choice;
+}
 async function promptScaffoldFramework() {
 	const choice = await Ee({
 		message: "Choose a Pages framework to scaffold:",
@@ -1850,11 +1920,12 @@ function generateStarterMigration(root, starterMode) {
 	}
 	R.success("Generated initial Drizzle migration");
 }
-function scaffoldPagesApp(root, packageManager, framework, starterMode) {
+function scaffoldPagesApp(root, packageManager, framework, starterMode, toolchain) {
 	const packageJsonPath = join(root, "package.json");
 	const template = createPagesStarterTemplate({
 		framework,
 		starterMode,
+		toolchain,
 		voidPackageSpec: resolveScaffoldDependencySpec(root, "void", getOwnVersion()),
 		adapterPackageSpec: resolveScaffoldDependencySpec(root, SCAFFOLD_FRAMEWORKS[framework].adapterPackage, getOwnVersion())
 	});
@@ -1893,7 +1964,7 @@ function scaffoldPagesApp(root, packageManager, framework, starterMode) {
 	for (const [name, version] of Object.entries(template.dependencies)) ensureDependency("dependencies", name, version);
 	for (const [name, version] of Object.entries(template.devDependencies)) ensureDependency("devDependencies", name, version);
 	if (isPnpmProject(root, pkg)) ensurePnpmAllowBuilds(root, pkg);
-	if (packageManager === "pnpm" && (!pkg.packageManager || typeof pkg.packageManager !== "string")) pkg.packageManager = "pnpm@11.0.9";
+	if (packageManager === "pnpm" && resolveWorkspaceDeferral(root, pkg) === void 0 && (!pkg.packageManager || typeof pkg.packageManager !== "string")) pkg.packageManager = "pnpm@11.0.9";
 	writeFileSync(packageJsonPath, JSON.stringify(pkg, null, 2) + "\n");
 	R.success("Updated package.json with starter scripts and dependencies");
 	for (const [filePath, content] of Object.entries(template.files)) writeFileIfMissing(root, filePath, content);
@@ -2547,6 +2618,7 @@ async function runInitCommand(root, initArgs) {
 	console.log();
 	ge(cliTitle("init"));
 	const targeted = Boolean(initArgs && (initArgs.tsconfig || initArgs.github || initArgs.agents));
+	if (!targeted) root = await resolveInitRoot(root);
 	const framework = detectFramework(root);
 	const preScaffoldState = detectProjectState(root);
 	const detectedPagesFramework = detectPagesFramework(root);
@@ -2558,12 +2630,14 @@ async function runInitCommand(root, initArgs) {
 	if (framework) R.info(`Detected ${framework.name} framework`);
 	if (!targeted && !framework && isScaffoldableEmptyProject(root)) {
 		R.info("Empty project detected. Scaffolding a Pages starter...");
+		const scaffoldToolchain = await promptScaffoldToolchain();
 		if (detectedPagesFramework) {
 			scaffoldedPagesFramework = detectedPagesFramework;
 			R.info(`Detected ${SCAFFOLD_FRAMEWORKS[detectedPagesFramework].label} adapter in package.json`);
 		} else scaffoldedPagesFramework = await promptScaffoldFramework();
 		const starterMode = await promptStarterMode();
-		const scaffoldWroteDeps = scaffoldPagesApp(root, preScaffoldState.packageManager, scaffoldedPagesFramework, starterMode);
+		const scaffoldPackageManager = scaffoldToolchain === "vite-plus" ? "pnpm" : preScaffoldState.packageManager;
+		const scaffoldWroteDeps = scaffoldPagesApp(root, scaffoldPackageManager, scaffoldedPagesFramework, starterMode, scaffoldToolchain);
 		const deferral = resolveWorkspaceDeferral(root, readPackageJson(root));
 		const voidResolvable = isVoidResolvableFrom(root);
 		if (deferral && (!voidResolvable || scaffoldWroteDeps)) {

package/dist/pages/islands-plugin.mjs

@@ -5,6 +5,11 @@ import { normalizePath } from "vite";
 //#region src/pages/islands-plugin.ts
 const ISLANDS_RENDERER_ID = "virtual:void-islands-renderer";
 const ISLANDS_CLIENT_ENTRY_ID = "virtual:void-islands-client";
+const ISLAND_IMPORT_RE = /import\s+([$_A-Za-z][$_\w]*)\s+from\s+("[^"]+"|'[^']+')\s+with\s*\{\s*island\s*:\s*("[^"]+"|'[^']+')\s*,?\s*\}/g;
+function hasIslandImports(code) {
+	ISLAND_IMPORT_RE.lastIndex = 0;
+	return ISLAND_IMPORT_RE.test(code);
+}
 /** Resolve a relative import specifier to an absolute path by checking extensions. */
 function resolveSpecifier(specifier, importerDir, extensions) {
 	const base = normalizePath(resolve(importerDir, specifier));
@@ -18,7 +23,6 @@ function resolveSpecifier(specifier, importerDir, extensions) {
 * or any .md file has a `<script>` block.
 */
 function needsIslandClientBundle(dir, islandFilePattern, checkStyleBlocks) {
-	const importAttrRe = /import\s+\w+\s+from\s+("[^"]+"|'[^']+')\s+with\s*\{\s*island\s*:/;
 	const cssImportRe = /import\b[^"']*["'][^"']+\.(?:css|scss|sass|less|styl|stylus|pcss|postcss)["']/;
 	const mdScriptRe = /^<script\b/m;
 	const styleRe = checkStyleBlocks ? /<style\b/ : null;
@@ -31,7 +35,7 @@ function needsIslandClientBundle(dir, islandFilePattern, checkStyleBlocks) {
 			const name = entry.name;
 			if (islandFilePattern.test(name) || name.startsWith("layout.") || name.startsWith("_")) {
 				const content = readFileSync(resolve(entry.parentPath, name), "utf-8");
-				if (importAttrRe.test(content)) return true;
+				if (hasIslandImports(content)) return true;
 				if (styleRe && styleRe.test(content)) return true;
 				if (cssImportRe.test(content)) return true;
 			}
@@ -67,13 +71,10 @@ function extractCssImports(filePath) {
 function computePagesNeedingClientJS(pageScan, pagesDir, resolvedConfig) {
 	const mdPlugin = resolvedConfig?.plugins?.find((plugin) => plugin.name === "void-md");
 	const mdScriptIds = new Set(mdPlugin?.api?.getClientScripts?.()?.keys() ?? []);
-	const importAttrRe = /import\s+\w+\s+from\s+("[^"]+"|'[^']+')\s+with\s*\{\s*island\s*:\s*("[^"]+"|'[^']+')\s*\}/g;
 	const layoutDirsWithIslands = /* @__PURE__ */ new Set();
 	for (const layout of pageScan.layouts) {
 		if (!layout.island) continue;
-		const code = readFileSync(resolve(pagesDir, layout.filePath), "utf-8");
-		importAttrRe.lastIndex = 0;
-		if (importAttrRe.test(code)) layoutDirsWithIslands.add(layout.directory);
+		if (hasIslandImports(readFileSync(resolve(pagesDir, layout.filePath), "utf-8"))) layoutDirsWithIslands.add(layout.directory);
 	}
 	const result = /* @__PURE__ */ new Set();
 	for (const page of pageScan.pages) {
@@ -82,9 +83,7 @@ function computePagesNeedingClientJS(pageScan, pagesDir, resolvedConfig) {
 			result.add(page.componentId);
 			continue;
 		}
-		const code = readFileSync(resolve(pagesDir, page.componentPath), "utf-8");
-		importAttrRe.lastIndex = 0;
-		if (importAttrRe.test(code)) {
+		if (hasIslandImports(readFileSync(resolve(pagesDir, page.componentPath), "utf-8"))) {
 			result.add(page.componentId);
 			continue;
 		}

package/dist/runtime/migration-handler.mjs

@@ -63,7 +63,8 @@ async function runD1Migrations(db, migrations) {
 		const start = Date.now();
 		try {
 			const statements = splitMigrationSql(m.sql);
-			if (statements.length === 1 && statements[0] === m.sql) await db.exec(m.sql);
+			if (statements.length === 1) if (isSingleSqlStatement(statements[0])) await db.prepare(statements[0]).run();
+			else await db.exec(m.sql);
 			else for (const statement of statements) await db.prepare(statement).run();
 			await db.prepare("INSERT OR IGNORE INTO _void_migrations (name, applied_at) VALUES (?, ?)").bind(m.name, (/* @__PURE__ */ new Date()).toISOString()).run();
 			migrationResults.push({
@@ -121,5 +122,71 @@ function isStatementBreakpointLine(line) {
 function hasInlineStatementBreakpoint(line) {
 	return /;\s*-->\s*statement-breakpoint\s*$/.test(line.trim());
 }
+function isSingleSqlStatement(sql) {
+	let statements = 0;
+	let inStatement = false;
+	let index = 0;
+	while (index < sql.length) {
+		const character = sql[index];
+		const next = index + 1 < sql.length ? sql[index + 1] : "";
+		if (character === "-" && next === "-") {
+			index += 2;
+			while (index < sql.length && sql[index] !== "\n") index++;
+			continue;
+		}
+		if (character === "/" && next === "*") {
+			index += 2;
+			while (index < sql.length - 1 && !(sql[index] === "*" && sql[index + 1] === "/")) index++;
+			index = Math.min(index + 2, sql.length);
+			continue;
+		}
+		if (character === "'") {
+			inStatement = true;
+			index++;
+			while (index < sql.length) {
+				if (sql[index] === "'" && sql[index + 1] === "'") {
+					index += 2;
+					continue;
+				}
+				if (sql[index] === "'") {
+					index++;
+					break;
+				}
+				index++;
+			}
+			continue;
+		}
+		if (character === "\"" || character === "`" || character === "[") {
+			inStatement = true;
+			const close = character === "[" ? "]" : character;
+			index++;
+			while (index < sql.length) {
+				if (close !== "]" && sql[index] === close && sql[index + 1] === close) {
+					index += 2;
+					continue;
+				}
+				if (sql[index] === close) {
+					index++;
+					break;
+				}
+				index++;
+			}
+			continue;
+		}
+		if (character === ";") {
+			if (inStatement) {
+				statements++;
+				if (statements > 1) return false;
+				inStatement = false;
+			}
+			index++;
+			continue;
+		}
+		if (character !== " " && character !== "	" && character !== "\n" && character !== "\r") inStatement = true;
+		index++;
+	}
+	if (inStatement) statements++;
+	return statements === 1;
+}
 //#endregion
 export { createMigrationHandler };

package/getting-started-prompt.txt

@@ -7,9 +7,9 @@ Then run:
 
 npx void init
 
-In an empty directory, `void init` will add the matching Pages adapter and starter dependencies after you choose a framework. In an existing app, it configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`.
+In an empty directory, `void init` will add the matching Pages adapter and starter dependencies after you choose a scaffold toolchain and framework. Vite+ is the default toolchain. In an existing app, it configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`.
 
-During `void init`, first choose a Pages framework (React, Vue, Svelte, or Solid), then choose D1 for a zero-config, fully managed default or PostgreSQL if you already have Postgres infrastructure or expect heavier writes and more complex queries.
+During `void init`, choose Vite+ unless you specifically want plain Vite scripts, then choose a Pages framework (React, Vue, Svelte, or Solid). Choose D1 for a zero-config, fully managed default or PostgreSQL if you already have Postgres infrastructure or expect heavier writes and more complex queries.
 
 At the end of the interactive flow, `void init` can also log you in and link or create your Void project so your first deploy is just:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "void",
-  "version": "0.7.12",
+  "version": "0.7.13",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/voidzero-dev/void.git",
@@ -332,7 +332,7 @@
     "valibot": ">=1.0.0-beta.7",
     "vite": "^8.0.0",
     "zod": "^3.25.0 || ^4.0.0",
-    "@void/md": "0.7.12"
+    "@void/md": "0.7.13"
   },
   "peerDependenciesMeta": {
     "@void/md": {

package/skills/void/SKILL.md

@@ -13,7 +13,7 @@ Docs in this skill are bundled from `docs/` during `void` package build and live
 
 ## Command Naming
 
-Use `void` in examples and commands in this skill. For first-time setup, prefer `void init` followed by `void deploy`; in an empty directory, install `void` first and let `void init` add the matching Pages adapter and starter dependencies. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. `void init` can also handle auth and project linking interactively.
+Use `void` in examples and commands in this skill. For first-time setup, prefer `void init` followed by `void deploy`; in an empty directory, install `void` first and let `void init` add the matching Pages adapter and starter dependencies with Vite+ as the default scaffold toolchain. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. `void init` can also handle auth and project linking interactively.
 
 Use `void` and `@void/*` in code examples and package manifests.
 

package/skills/void/docs/guide/pages-routing/overview.md

@@ -12,7 +12,7 @@ Pages mode is also entirely optional - you can use any client-side router to bui
 
 ## Setup
 
-If you start in a scaffoldable empty directory, `void init` can generate this setup for you: it asks whether you want React, Vue, Svelte, or Solid Pages mode, then lets you pick a D1 starter, a PostgreSQL starter, or Static Pages. The database-backed starters write the adapter-aware `vite.config.ts`, `pages/`, and `db/` starter files; Static Pages writes just the basic `pages/` setup so you can grow into server features later.
+If you start in a scaffoldable empty directory, `void init` can generate this setup for you: it asks whether to scaffold with Vite+ (the default) or plain Vite, asks whether you want React, Vue, Svelte, or Solid Pages mode, then lets you pick a D1 starter, a PostgreSQL starter, or Static Pages. The database-backed starters write the adapter-aware `vite.config.ts`, `pages/`, and `db/` starter files; Static Pages writes just the basic `pages/` setup so you can grow into server features later.
 
 If you're adding Pages mode manually, install a framework adapter alongside `void`:
 

package/skills/void/docs/guide/quickstart.md

@@ -32,9 +32,9 @@ yarn add -D void
 bun add -D void
 ```
 
-In an empty directory, `void init` adds the matching Pages adapter and starter dependencies after you choose a framework.
+In an empty directory, `void init` adds the matching Pages adapter and starter dependencies after you choose a scaffold toolchain and framework. Vite+ is the default toolchain and uses `vp` scripts.
 
-As part of `void init`, you'll choose a Pages framework (React, Vue, Svelte, or Solid) and a starter type. D1 is the default top option and scaffolds a DB-backed page loader, schema, generated migration, `db/seed.ts`, and API route. PostgreSQL scaffolds the same starter and writes `"database": "pg"` to `void.json`. Static Pages skips the database and server starter files so you can start with static content and add Void features later.
+As part of `void init`, you'll choose Vite+ or plain Vite, then a Pages framework (React, Vue, Svelte, or Solid) and a starter type. D1 is the default top option and scaffolds a DB-backed page loader, schema, generated migration, `db/seed.ts`, and API route. PostgreSQL scaffolds the same starter and writes `"database": "pg"` to `void.json`. Static Pages skips the database and server starter files so you can start with static content and add Void features later.
 
 After installation, run the setup flow:
 

package/skills/void/docs/node_modules/void/AGENT_PROMPT.md

@@ -1,6 +1,6 @@
 ## Void
 
-This project uses [Void](https://void.cloud) — a fullstack Vite plugin + deployment platform for Cloudflare. `voidPlugin()` in `vite.config.ts` gives you file-based API routing on Hono (`routes/`), Inertia-inspired server-rendered pages with co-located loaders/actions (`pages/` + `@void/vue` or `@void/react`), auto-provisioned D1/KV/R2 bindings, first-class Drizzle ORM integration (schema in `db/schema.ts` -> `void/db` Drizzle instance -> typed routes -> typed fetch client), built-in auth, queues, cron jobs, edge caching (ISR), and one-command deploys via `npx void deploy`. For first-time setup, prefer `npx void init`; in an empty directory, install `void` first and let the interactive flow scaffold the starter, add the matching framework adapter, configure project files, handle auth, and link or create the deploy project before the first deploy. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. Use `void` and `@void/*` package names in source code and package manifests.
+This project uses [Void](https://void.cloud) — a fullstack Vite plugin + deployment platform for Cloudflare. `voidPlugin()` in `vite.config.ts` gives you file-based API routing on Hono (`routes/`), Inertia-inspired server-rendered pages with co-located loaders/actions (`pages/` + `@void/vue` or `@void/react`), auto-provisioned D1/KV/R2 bindings, first-class Drizzle ORM integration (schema in `db/schema.ts` -> `void/db` Drizzle instance -> typed routes -> typed fetch client), built-in auth, queues, cron jobs, edge caching (ISR), and one-command deploys via `npx void deploy`. For first-time setup, prefer `npx void init`; in an empty directory, install `void` first and let the interactive flow scaffold the starter with Vite+ by default, add the matching framework adapter, configure project files, handle auth, and link or create the deploy project before the first deploy. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. Use `void` and `@void/*` package names in source code and package manifests.
 
 Database: define Drizzle tables in `db/schema.ts`, import `db` from `void/db` and tables from `@schema`. Use `void db push` for prototyping, `void db generate` for production migrations. `drizzle-orm` and `drizzle-kit` ship with void (no extra install). Migrations live in `db/migrations/`.
 

package/skills/void/docs/node_modules/void/README.md

@@ -21,7 +21,7 @@ Install the Void CLI:
 npm install -D void
 ```
 
-If you run `void init` in an empty directory, the scaffold flow adds the matching Pages adapter and Vite dependencies for you.
+If you run `void init` in an empty directory, the scaffold flow adds the matching Pages adapter and Vite+ by default.
 
 Then run `npx void init`. In an empty directory, the full interactive flow can scaffold a starter, configure local project files, log you in, and link or create your Void project so the next step is just `npx void deploy`. In an existing app, it configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`.
 
@@ -82,7 +82,7 @@ There is Vinext-specific source in the repo, but it is intentionally on hold and
 
 ## Documentation
 
-Full docs live at [void.cloud/docs](https://void.cloud/docs).
+Full docs live at [void.cloud/guide](https://void.cloud/guide).
 
 ## License
 

package/skills/void/docs/node_modules/void/skills/void/SKILL.md

@@ -13,7 +13,7 @@ Docs in this skill are bundled from `docs/` during `void` package build and live
 
 ## Command Naming
 
-Use `void` in examples and commands in this skill. For first-time setup, prefer `void init` followed by `void deploy`; in an empty directory, install `void` first and let `void init` add the matching Pages adapter and starter dependencies. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. `void init` can also handle auth and project linking interactively.
+Use `void` in examples and commands in this skill. For first-time setup, prefer `void init` followed by `void deploy`; in an empty directory, install `void` first and let `void init` add the matching Pages adapter and starter dependencies with Vite+ as the default scaffold toolchain. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. `void init` can also handle auth and project linking interactively.
 
 Use `void` and `@void/*` in code examples and package manifests.
 

package/skills/void/docs/reference/cli.md

@@ -66,7 +66,9 @@ void init [--tsconfig] [--github] [--agents]
 
 Setup wizard for Void projects (new or existing).
 
-If run in a scaffoldable empty directory, `void init` scaffolds a Pages starter. If a single Pages adapter is already installed, it reuses that framework; otherwise it asks which framework to scaffold (React, Vue, Svelte, or Solid). It then asks which starter you want: D1, PostgreSQL, or Static Pages. The D1 and PostgreSQL starters write a framework-specific `vite.config.ts`, a `pages/` home page plus `.server.ts` loader, `db/schema.ts`, `db/seed.ts`, a generated initial migration under `db/migrations/`, and `routes/api/hello.ts`. The Static Pages starter writes just the framework-specific `vite.config.ts` and a `pages/` home page so you can add server features later.
+If run in a scaffoldable empty directory, `void init` scaffolds a Pages starter. It asks which scaffold toolchain to use, with Vite+ as the default top option and plain Vite as the alternative. If a single Pages adapter is already installed, it reuses that framework; otherwise it asks which framework to scaffold (React, Vue, Svelte, or Solid). It then asks which starter you want: D1, PostgreSQL, or Static Pages. The D1 and PostgreSQL starters write a framework-specific `vite.config.ts`, a `pages/` home page plus `.server.ts` loader, `db/schema.ts`, `db/seed.ts`, a generated initial migration under `db/migrations/`, and `routes/api/hello.ts`. The Static Pages starter writes just the framework-specific `vite.config.ts` and a `pages/` home page so you can add server features later. Vite+ starters add `vite-plus` and use `vp dev`, `vp build`, and `vp preview` scripts.
+
+If run in a non-empty folder that does not look like an app yet, such as a parent `Projects/` folder with subdirectories but no `package.json`, `void init` asks whether to create a new subfolder or continue in the current folder. Creating a subfolder is the default selection.
 
 If run in an existing project, `void init` configures the project in place: it ensures `void` and `vite` are declared, adds missing `dev` (`vite`) and `build` (`vite build`) scripts without overwriting existing scripts, and creates or patches `vite.config.*` with `voidPlugin()` when the config shape is safe to edit. If the Vite config is too dynamic to patch confidently, it prints the manual snippet instead of rewriting it.