@devdogsuga/devtools 0.1.51-next.544 → 0.1.51-next.545

package/README.md

@@ -97,12 +97,15 @@ name `devdogs-monorepo` or `backstage`; the layout code is
 
 A repository with a `devtools.config.json` at its root is a **product** (DogDays, DogPack): devtools
 reads the file and serves a smaller command set that needs no tiers, no env registry and no workspace.
-DogPack has no `package.json`, so it runs the published CLI directly:
+Both products carry a `package.json` whose `devtools` script is a `pnpm dlx` run of the published CLI, so
+inside a checkout:
 
 ```sh
-npx @devdogsuga/devtools@next setup
+pnpm devtools setup
 ```
 
+Anywhere else, the one-off form is `pnpm dlx @devdogsuga/devtools@next setup`.
+
 | Command                                 | What it does                                                                                                                                                               |
 | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `setup [--local \| --hosted]`           | Writes `.env` from `.env.example`; starts the Docker stack (or takes your own hosted project's URL, keys and session-pooler `DB_URL`); `db sync`; the types; then `oauth`. |
@@ -136,7 +139,7 @@ How it works, in short:
   `oauth` (the tooling file) check that they are git-ignored and add them to the repo's `.gitignore`
   when they are not (Flutter's default ignore file leaves them out).
 - **The pinned CLI.** devtools finds `supabase` in `node_modules/.bin` or on PATH when its version is the
-  pin, and otherwise runs `npx --yes supabase@<pin>`.
+  pin, and otherwise runs `pnpm dlx supabase@<pin>` (`npx --yes supabase@<pin>` only when pnpm is not on PATH).
 - **A hosted project** needs custom OAuth providers turned on and the app's return addresses allowed.
   `setup` does both through the Management API when `SUPABASE_ACCESS_TOKEN` is set, and prints the two
   dashboard steps when it is not.

package/dist/{cli-D98LfCHU.js → cli-DNZ-6WEI.js}

@@ -4920,7 +4920,7 @@ function productPin(cwd) {
 * a sibling project, where the Supabase CLI is normally installed globally;
 * this monorepo, where it is a workspace devDependency and not on PATH at all;
 * and a product repo (`devtools.config.json`), where `devtools setup` ran the
-* pinned CLI through `npx` and a new member has none installed. A global install
+* pinned CLI through `pnpm dlx` and a new member has none installed. A global install
 * wins, since `pnpm exec` in a non-pnpm project would fail for reasons that have
 * nothing to do with Supabase.
 */
@@ -4942,19 +4942,32 @@ function detectLocalSupabase(cwd) {
 		...status
 	]];
 	const pin = productPin(cwd);
-	if (pin !== null) attempts.push([
-		"npx",
-		"--yes",
-		`supabase@${pin}`,
-		...status
-	]);
+	if (pin !== null) {
+		attempts.push([
+			"pnpm",
+			"dlx",
+			`supabase@${pin}`,
+			...status
+		]);
+		attempts.push([
+			"npx",
+			"--yes",
+			`supabase@${pin}`,
+			...status
+		]);
+	}
 	let output;
 	let first;
-	for (const argv of attempts) try {
-		output = runStatus(argv, cwd);
-		break;
-	} catch (error) {
-		first ??= error;
+	let pnpmMissing = false;
+	for (const argv of attempts) {
+		if (argv[0] === "npx" && !pnpmMissing) continue;
+		try {
+			output = runStatus(argv, cwd);
+			break;
+		} catch (error) {
+			first ??= error;
+			if (argv[0] === "pnpm" && error.code === "ENOENT") pnpmMissing = true;
+		}
 	}
 	if (output === void 0) {
 		if (first.code === "ENOENT") throw new Error("supabase CLI not found — install it from https://supabase.com/docs/guides/cli");
@@ -7034,7 +7047,9 @@ function commandLine(command, args) {
 *
 *   1. `node_modules/.bin/supabase` in the repo, when its version is the pin;
 *   2. a `supabase` on PATH whose version is the pin;
-*   3. `npx --yes supabase@<pin>`, which downloads and caches the right one.
+*   3. `pnpm dlx supabase@<pin>`, which downloads and caches the right one.
+*      Members are expected to have pnpm (both product repos pin it);
+*   4. `npx --yes supabase@<pin>`, only when pnpm is not on PATH.
 *
 * The pin is also part of the generated-types hash, so a contributor on a
 * different CLI would generate different types than CI; matching it is not
@@ -7063,6 +7078,13 @@ async function resolveSupabaseCli(root, pin, run, fileExists = existsSync) {
 		const result = await run(candidate.command, ["--version"], { cwd: root });
 		if (result.code === 0 && versionOf(result.stdout) === pin) return candidate;
 	} catch {}
+	try {
+		if ((await run("pnpm", ["--version"], { cwd: root })).code === 0) return {
+			command: "pnpm",
+			prefix: ["dlx", `supabase@${pin}`],
+			source: "pnpm"
+		};
+	} catch {}
 	return {
 		command: "npx",
 		prefix: ["--yes", `supabase@${pin}`],
@@ -8051,7 +8073,7 @@ async function runDoctor(product, deps) {
 	const info = (message) => void lines.push(`INFO  ${message}`);
 	ok(`${product.config.name} (${product.config.product}), Supabase CLI pinned at ${product.config.supabase.version}`);
 	const cli = await cliFor(product, deps);
-	if (cli.source === "npx") info(`The pinned Supabase CLI is fetched with npx on first use (${cliLine(cli, ["--version"])}).`);
+	if (cli.source === "pnpm" || cli.source === "npx") info(`The pinned Supabase CLI is fetched with ${cli.command} on first use (${cliLine(cli, ["--version"])}).`);
 	else ok(`Supabase CLI ${product.config.supabase.version} (${cli.source})`);
 	const docker = await deps.run("docker", [
 		"info",

package/dist/launch.js

@@ -183,7 +183,7 @@ async function startStack() {
 * post-tier-resolution path.
 */
 async function dispatch(argv) {
-	const { main } = await import("./cli-D98LfCHU.js");
+	const { main } = await import("./cli-DNZ-6WEI.js");
 	try {
 		await main(argv);
 	} catch (err) {

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@devdogsuga/devtools",
-  "version": "0.1.51-next.544",
+  "version": "0.1.51-next.545",
   "private": false,
   "type": "module",
-  "description": "Contributor CLI for DevDogs repositories (the platform monorepo, DogDays, DogPack): the real tools with the session's tier filled in, `setup`, `db sync`, `db types`, `dev-data`, a menu over them, the checks CI runs, and the `with-env` launcher. Ships built JS; run via `pnpm dlx @devdogsuga/devtools` or `npx @devdogsuga/devtools` (or the `devtools` bin once installed) from inside a clone.",
+  "description": "Contributor CLI for DevDogs repositories (the platform monorepo, DogDays, DogPack): the real tools with the session's tier filled in, `setup`, `db sync`, `db types`, `dev-data`, a menu over them, the checks CI runs, and the `with-env` launcher. Ships built JS; run via `pnpm devtools` in a product repo, `pnpm dlx @devdogsuga/devtools` (or the `devtools` bin once installed) from inside a clone.",
   "license": "BSD-3-Clause",
   "repository": {
     "type": "git",
@@ -47,8 +47,8 @@
     "tsdown": "^0.23.0",
     "vitest": "^4.1.11",
     "@devdogsuga/cli-core": "0.0.0",
-    "@devdogsuga/sdk": "0.1.0",
-    "@devdogsuga/config": "0.1.4-next.526"
+    "@devdogsuga/config": "0.1.4-next.526",
+    "@devdogsuga/sdk": "0.1.0"
   },
   "scripts": {
     "build": "tsdown && node scripts/write-build-info.mjs && node ../../scripts/check-bundle-imports.mjs",