config-vp 1.2.0 → 1.2.1

package/README.md

@@ -213,6 +213,25 @@ Run any task with `vp run <task>`. Tasks are cached and run in dependency order
 
 > For a whole-workspace lint/format, use the built-in `vp check`. To build every package, use `vp run -r build`.
 
+### Overriding a task with a package.json script
+
+**Your `package.json` scripts win.** If a package defines a script with the same name as a generated task, config-vp drops its own task and your script takes over — no clash, no config needed:
+
+```jsonc
+// package.json
+{
+  "scripts": {
+    "build": "tsx scripts/build.ts", // replaces the generated `build` task
+  },
+}
+```
+
+```sh
+vp run build   # runs your script, not `vp pack`
+```
+
+This is the simplest way to special-case one task while keeping every other default. (Without it, `vp` errors with _"Task `build` conflicts with a package.json script of the same name"_.) For richer changes — tweaking a task's command, cache behavior, or adding new tasks — use the [`config` hook](#customizing) instead; reach for a script only when you want to shadow a task outright.
+
 ## Customizing
 
 There's one customization hook: **`config`**. It receives the fully built config — lint, fmt, staged, run tasks, and (for `lib*`) pack, all already populated — and you change whatever you want with plain JS. Mutate it in place, or return a new object (a returned value wins; otherwise the mutated argument is used). It's fully typed, so autocomplete shows you exactly what's there.

package/dist/index.mjs

@@ -531,6 +531,16 @@ function callerPackageDir() {
 		if (direct && !direct[1].includes("/node_modules/")) return direct[1];
 	}
 }
+/** Script names in the calling package's package.json — these override our generated tasks. */
+function packageScriptNames() {
+	const dir = callerPackageDir() ?? process.cwd();
+	try {
+		const pkg = JSON.parse(readFileSync(join(dir, "package.json"), "utf8"));
+		return new Set(Object.keys(pkg.scripts ?? {}));
+	} catch {
+		return /* @__PURE__ */ new Set();
+	}
+}
 /** True when the calling config's package is the workspace root (or a standalone project). */
 function isProjectRoot() {
 	const dir = callerPackageDir() ?? process.cwd();
@@ -590,7 +600,8 @@ function buildRunConfig(options = {}) {
 		command: "vp-setup-vscode",
 		cache: false
 	};
-	return { tasks };
+	const scripts = packageScriptNames();
+	return { tasks: Object.fromEntries(Object.entries(tasks).filter(([name]) => !scripts.has(name))) };
 }
 //#endregion
 //#region src/staged.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "config-vp",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "Shared vite-plus configuration — opinionated defaults for linting, formatting, task running, staged checks, and VSCode setup. Optional Vue and pack layers with deep-merge overrides.",
   "keywords": [
     "config",