@geekmidas/cli 10.0.0-alpha.122 → 10.0.0-alpha.124

package/dist/run-BJLIerMM.mjs

@@ -1,133 +0,0 @@
-import { join, resolve } from "node:path";
-import { homedir } from "node:os";
-import { spawn } from "node:child_process";
-//#region src/home.ts
-/**
-* Where the CLI keeps what belongs to a person rather than a project: stage
-* keys and stored provider credentials.
-*
-* `GKM_HOME` names it, so a CI job, a shared build runner or a test can give
-* every run its own instead of reaching into whoever's home directory the
-* process happens to have. Unset, it is `~/.gkm`, where it has always been.
-*/
-/** The environment variable that moves the CLI's home. */
-const GKM_HOME_ENV = "GKM_HOME";
-/** The CLI's home: `GKM_HOME` if set, else `~/.gkm`. */
-function gkmHome(env = process.env) {
-	const configured = env[GKM_HOME_ENV];
-	return configured ? resolve(configured) : join(homedir(), ".gkm");
-}
-//#endregion
-//#region src/run.ts
-/**
-* Start a program with an argument array, never a shell string.
-*
-* `gkm build`, `gkm docker` and `gkm deploy` pass values that come from the
-* workspace — image refs, tags, build args, package names — to `docker` and
-* `turbo`. Joined into a string and handed to a shell, a package named
-* `x;curl …|sh` or a tag holding `$(…)` became part of the command line, which
-* matters most where the CLI builds a repository it didn't write: a CI job for a
-* fork, a shared build runner. Here every value reaches the program as one
-* `argv` element, whatever it contains.
-*/
-/** Long enough for a cold image build; short enough that a hung one ends. */
-const DEFAULT_TIMEOUT_MS = 18e5;
-/** How long a timed-out child has to exit on SIGTERM before it is killed. */
-const KILL_GRACE_MS = 5e3;
-/** The command line as a person would read it — for messages, never to run. */
-function display(command, args) {
-	return [command, ...args].join(" ");
-}
-/** The program ran and exited unsuccessfully; its own output said why. */
-var CommandFailed = class extends Error {
-	command;
-	args;
-	exitCode;
-	signal;
-	constructor(command, args, exitCode, signal) {
-		super(`\`${display(command, args)}\` ${exitCode === null ? `was stopped by ${signal ?? "a signal"}` : `exited with code ${exitCode}`}. Its output above says why; run it by hand to see it again.`);
-		this.command = command;
-		this.args = args;
-		this.exitCode = exitCode;
-		this.signal = signal;
-		this.name = "CommandFailed";
-	}
-};
-/** The program ran past its timeout and was killed. */
-var CommandTimedOut = class extends Error {
-	command;
-	args;
-	timeoutMs;
-	constructor(command, args, timeoutMs) {
-		super(`\`${display(command, args)}\` was still running after ${Math.round(timeoutMs / 1e3)}s and was stopped. Check what it was waiting on — a registry, the Docker daemon, a prompt — and run it again.`);
-		this.command = command;
-		this.args = args;
-		this.timeoutMs = timeoutMs;
-		this.name = "CommandTimedOut";
-	}
-};
-/**
-* Run `command` with `args`, resolving when it exits 0.
-*
-* Rejects with {@link CommandFailed} on any other exit, {@link CommandTimedOut}
-* once `timeoutMs` passes (after the child is gone), and with the spawn error
-* itself when the program cannot be started at all — `ENOENT` already names it.
-*/
-async function run(command, args, options = {}) {
-	await spawnChild(command, args, options, false);
-}
-/**
-* {@link run}, resolving with what the program wrote to stdout — for a value
-* the CLI reads back, such as the digest `docker inspect` reports. stderr still
-* reaches the terminal, so a failure explains itself the same way.
-*/
-function runOutput(command, args, options = {}) {
-	return spawnChild(command, args, options, true);
-}
-function spawnChild(command, args, options, capture) {
-	const { timeoutMs = DEFAULT_TIMEOUT_MS, ...spawnOptions } = options;
-	return new Promise((resolve, reject) => {
-		const child = spawn(command, [...args], {
-			stdio: "inherit",
-			...spawnOptions,
-			...capture ? { stdio: [
-				"ignore",
-				"pipe",
-				"inherit"
-			] } : {},
-			shell: false
-		});
-		let stdout = "";
-		child.stdout?.on("data", (chunk) => {
-			stdout += chunk.toString();
-		});
-		let timedOut = false;
-		let killer;
-		const timer = setTimeout(() => {
-			timedOut = true;
-			child.kill("SIGTERM");
-			killer = setTimeout(() => child.kill("SIGKILL"), KILL_GRACE_MS);
-			killer.unref?.();
-		}, timeoutMs);
-		timer.unref?.();
-		const settle = () => {
-			clearTimeout(timer);
-			if (killer) clearTimeout(killer);
-		};
-		child.on("error", (error) => {
-			settle();
-			reject(spawnOptions.signal?.aborted ? spawnOptions.signal.reason : error);
-		});
-		child.on("close", (code, signal) => {
-			settle();
-			if (spawnOptions.signal?.aborted) reject(spawnOptions.signal.reason);
-			else if (timedOut) reject(new CommandTimedOut(command, args, timeoutMs));
-			else if (code === 0) resolve(stdout);
-			else reject(new CommandFailed(command, args, code, signal));
-		});
-	});
-}
-//#endregion
-export { runOutput as a, run as i, CommandTimedOut as n, GKM_HOME_ENV as o, DEFAULT_TIMEOUT_MS as r, gkmHome as s, CommandFailed as t };
-
-//# sourceMappingURL=run-BJLIerMM.mjs.map

package/dist/run-BJLIerMM.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"run-BJLIerMM.mjs","names":[],"sources":["../src/home.ts","../src/run.ts"],"sourcesContent":["/**\n * Where the CLI keeps what belongs to a person rather than a project: stage\n * keys and stored provider credentials.\n *\n * `GKM_HOME` names it, so a CI job, a shared build runner or a test can give\n * every run its own instead of reaching into whoever's home directory the\n * process happens to have. Unset, it is `~/.gkm`, where it has always been.\n */\n\nimport { homedir } from 'node:os';\nimport { join, resolve } from 'node:path';\n\n/** The environment variable that moves the CLI's home. */\nexport const GKM_HOME_ENV = 'GKM_HOME';\n\n/** The CLI's home: `GKM_HOME` if set, else `~/.gkm`. */\nexport function gkmHome(env: NodeJS.ProcessEnv = process.env): string {\n\tconst configured = env[GKM_HOME_ENV];\n\treturn configured ? resolve(configured) : join(homedir(), '.gkm');\n}\n","/**\n * Start a program with an argument array, never a shell string.\n *\n * `gkm build`, `gkm docker` and `gkm deploy` pass values that come from the\n * workspace — image refs, tags, build args, package names — to `docker` and\n * `turbo`. Joined into a string and handed to a shell, a package named\n * `x;curl …|sh` or a tag holding `$(…)` became part of the command line, which\n * matters most where the CLI builds a repository it didn't write: a CI job for a\n * fork, a shared build runner. Here every value reaches the program as one\n * `argv` element, whatever it contains.\n */\n\nimport { type SpawnOptions, spawn } from 'node:child_process';\n\n/** Long enough for a cold image build; short enough that a hung one ends. */\nexport const DEFAULT_TIMEOUT_MS = 30 * 60_000;\n\n/** How long a timed-out child has to exit on SIGTERM before it is killed. */\nconst KILL_GRACE_MS = 5_000;\n\nexport interface RunOptions {\n\tcwd?: string;\n\tenv?: NodeJS.ProcessEnv;\n\tstdio?: SpawnOptions['stdio'];\n\t/** Kill the child after this long. Defaults to {@link DEFAULT_TIMEOUT_MS}. */\n\ttimeoutMs?: number;\n\t/**\n\t * Kills the child when aborted, and rejects with the signal's reason — the\n\t * same as a stopped deploy's other calls.\n\t */\n\tsignal?: AbortSignal;\n}\n\n/** The command line as a person would read it — for messages, never to run. */\nfunction display(command: string, args: readonly string[]): string {\n\treturn [command, ...args].join(' ');\n}\n\n/** The program ran and exited unsuccessfully; its own output said why. */\nexport class CommandFailed extends Error {\n\tconstructor(\n\t\treadonly command: string,\n\t\treadonly args: readonly string[],\n\t\treadonly exitCode: number | null,\n\t\treadonly signal: NodeJS.Signals | null,\n\t) {\n\t\tsuper(\n\t\t\t`\\`${display(command, args)}\\` ${exitCode === null ? `was stopped by ${signal ?? 'a signal'}` : `exited with code ${exitCode}`}. Its output above says why; run it by hand to see it again.`,\n\t\t);\n\t\tthis.name = 'CommandFailed';\n\t}\n}\n\n/** The program ran past its timeout and was killed. */\nexport class CommandTimedOut extends Error {\n\tconstructor(\n\t\treadonly command: string,\n\t\treadonly args: readonly string[],\n\t\treadonly timeoutMs: number,\n\t) {\n\t\tsuper(\n\t\t\t`\\`${display(command, args)}\\` was still running after ${Math.round(timeoutMs / 1000)}s and was stopped. Check what it was waiting on — a registry, the Docker daemon, a prompt — and run it again.`,\n\t\t);\n\t\tthis.name = 'CommandTimedOut';\n\t}\n}\n\n/**\n * Run `command` with `args`, resolving when it exits 0.\n *\n * Rejects with {@link CommandFailed} on any other exit, {@link CommandTimedOut}\n * once `timeoutMs` passes (after the child is gone), and with the spawn error\n * itself when the program cannot be started at all — `ENOENT` already names it.\n */\nexport async function run(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: RunOptions = {},\n): Promise<void> {\n\tawait spawnChild(command, args, options, false);\n}\n\n/**\n * {@link run}, resolving with what the program wrote to stdout — for a value\n * the CLI reads back, such as the digest `docker inspect` reports. stderr still\n * reaches the terminal, so a failure explains itself the same way.\n */\nexport function runOutput(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: Omit<RunOptions, 'stdio'> = {},\n): Promise<string> {\n\treturn spawnChild(command, args, options, true);\n}\n\nfunction spawnChild(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: RunOptions,\n\tcapture: boolean,\n): Promise<string> {\n\tconst { timeoutMs = DEFAULT_TIMEOUT_MS, ...spawnOptions } = options;\n\n\treturn new Promise<string>((resolve, reject) => {\n\t\tconst child = spawn(command, [...args], {\n\t\t\tstdio: 'inherit',\n\t\t\t...spawnOptions,\n\t\t\t...(capture ? { stdio: ['ignore', 'pipe', 'inherit'] } : {}),\n\t\t\tshell: false,\n\t\t});\n\n\t\tlet stdout = '';\n\t\tchild.stdout?.on('data', (chunk: Buffer) => {\n\t\t\tstdout += chunk.toString();\n\t\t});\n\n\t\tlet timedOut = false;\n\t\tlet killer: NodeJS.Timeout | undefined;\n\t\tconst timer = setTimeout(() => {\n\t\t\ttimedOut = true;\n\t\t\tchild.kill('SIGTERM');\n\t\t\t// A child that ignores SIGTERM would hold the deploy open forever.\n\t\t\tkiller = setTimeout(() => child.kill('SIGKILL'), KILL_GRACE_MS);\n\t\t\tkiller.unref?.();\n\t\t}, timeoutMs);\n\t\ttimer.unref?.();\n\n\t\tconst settle = () => {\n\t\t\tclearTimeout(timer);\n\t\t\tif (killer) clearTimeout(killer);\n\t\t};\n\n\t\tchild.on('error', (error) => {\n\t\t\tsettle();\n\t\t\t// Node reports an abort as its own `AbortError`; the caller asked\n\t\t\t// with a reason, and that is what it should get back.\n\t\t\treject(spawnOptions.signal?.aborted ? spawnOptions.signal.reason : error);\n\t\t});\n\n\t\tchild.on('close', (code: number | null, signal: NodeJS.Signals | null) => {\n\t\t\tsettle();\n\t\t\tif (spawnOptions.signal?.aborted) reject(spawnOptions.signal.reason);\n\t\t\telse if (timedOut) reject(new CommandTimedOut(command, args, timeoutMs));\n\t\t\telse if (code === 0) resolve(stdout);\n\t\t\telse reject(new CommandFailed(command, args, code, signal));\n\t\t});\n\t});\n}\n"],"mappings":";;;;;;;;;;;;;AAaA,MAAa,eAAe;;AAG5B,SAAgB,QAAQ,MAAyB,QAAQ,KAAa;CACrE,MAAM,aAAa,IAAI;CACvB,OAAO,aAAa,QAAQ,UAAU,IAAI,KAAK,QAAQ,GAAG,MAAM;AACjE;;;;;;;;;;;;;;;ACJA,MAAa,qBAAqB;;AAGlC,MAAM,gBAAgB;;AAgBtB,SAAS,QAAQ,SAAiB,MAAiC;CAClE,OAAO,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KAAK,GAAG;AACnC;;AAGA,IAAa,gBAAb,cAAmC,MAAM;CAE9B;CACA;CACA;CACA;CAJV,YACC,SACA,MACA,UACA,QACC;EACD,MACC,KAAK,QAAQ,SAAS,IAAI,EAAE,KAAK,aAAa,OAAO,kBAAkB,UAAU,eAAe,oBAAoB,WAAW,6DAChI;EAPS,KAAA,UAAA;EACA,KAAA,OAAA;EACA,KAAA,WAAA;EACA,KAAA,SAAA;EAKT,KAAK,OAAO;CACb;AACD;;AAGA,IAAa,kBAAb,cAAqC,MAAM;CAEhC;CACA;CACA;CAHV,YACC,SACA,MACA,WACC;EACD,MACC,KAAK,QAAQ,SAAS,IAAI,EAAE,6BAA6B,KAAK,MAAM,YAAY,GAAI,EAAE,8GACvF;EANS,KAAA,UAAA;EACA,KAAA,OAAA;EACA,KAAA,YAAA;EAKT,KAAK,OAAO;CACb;AACD;;;;;;;;AASA,eAAsB,IACrB,SACA,MACA,UAAsB,CAAC,GACP;CAChB,MAAM,WAAW,SAAS,MAAM,SAAS,KAAK;AAC/C;;;;;;AAOA,SAAgB,UACf,SACA,MACA,UAAqC,CAAC,GACpB;CAClB,OAAO,WAAW,SAAS,MAAM,SAAS,IAAI;AAC/C;AAEA,SAAS,WACR,SACA,MACA,SACA,SACkB;CAClB,MAAM,EAAE,YAAY,oBAAoB,GAAG,iBAAiB;CAE5D,OAAO,IAAI,SAAiB,SAAS,WAAW;EAC/C,MAAM,QAAQ,MAAM,SAAS,CAAC,GAAG,IAAI,GAAG;GACvC,OAAO;GACP,GAAG;GACH,GAAI,UAAU,EAAE,OAAO;IAAC;IAAU;IAAQ;GAAS,EAAE,IAAI,CAAC;GAC1D,OAAO;EACR,CAAC;EAED,IAAI,SAAS;EACb,MAAM,QAAQ,GAAG,SAAS,UAAkB;GAC3C,UAAU,MAAM,SAAS;EAC1B,CAAC;EAED,IAAI,WAAW;EACf,IAAI;EACJ,MAAM,QAAQ,iBAAiB;GAC9B,WAAW;GACX,MAAM,KAAK,SAAS;GAEpB,SAAS,iBAAiB,MAAM,KAAK,SAAS,GAAG,aAAa;GAC9D,OAAO,QAAQ;EAChB,GAAG,SAAS;EACZ,MAAM,QAAQ;EAEd,MAAM,eAAe;GACpB,aAAa,KAAK;GAClB,IAAI,QAAQ,aAAa,MAAM;EAChC;EAEA,MAAM,GAAG,UAAU,UAAU;GAC5B,OAAO;GAGP,OAAO,aAAa,QAAQ,UAAU,aAAa,OAAO,SAAS,KAAK;EACzE,CAAC;EAED,MAAM,GAAG,UAAU,MAAqB,WAAkC;GACzE,OAAO;GACP,IAAI,aAAa,QAAQ,SAAS,OAAO,aAAa,OAAO,MAAM;QAC9D,IAAI,UAAU,OAAO,IAAI,gBAAgB,SAAS,MAAM,SAAS,CAAC;QAClE,IAAI,SAAS,GAAG,QAAQ,MAAM;QAC9B,OAAO,IAAI,cAAc,SAAS,MAAM,MAAM,MAAM,CAAC;EAC3D,CAAC;CACF,CAAC;AACF"}

package/dist/run-fVZ-rLnc.cjs

@@ -1,174 +0,0 @@
-let node_path = require("node:path");
-let node_os = require("node:os");
-let node_child_process = require("node:child_process");
-//#region src/home.ts
-/**
-* Where the CLI keeps what belongs to a person rather than a project: stage
-* keys and stored provider credentials.
-*
-* `GKM_HOME` names it, so a CI job, a shared build runner or a test can give
-* every run its own instead of reaching into whoever's home directory the
-* process happens to have. Unset, it is `~/.gkm`, where it has always been.
-*/
-/** The environment variable that moves the CLI's home. */
-const GKM_HOME_ENV = "GKM_HOME";
-/** The CLI's home: `GKM_HOME` if set, else `~/.gkm`. */
-function gkmHome(env = process.env) {
-	const configured = env[GKM_HOME_ENV];
-	return configured ? (0, node_path.resolve)(configured) : (0, node_path.join)((0, node_os.homedir)(), ".gkm");
-}
-//#endregion
-//#region src/run.ts
-/**
-* Start a program with an argument array, never a shell string.
-*
-* `gkm build`, `gkm docker` and `gkm deploy` pass values that come from the
-* workspace — image refs, tags, build args, package names — to `docker` and
-* `turbo`. Joined into a string and handed to a shell, a package named
-* `x;curl …|sh` or a tag holding `$(…)` became part of the command line, which
-* matters most where the CLI builds a repository it didn't write: a CI job for a
-* fork, a shared build runner. Here every value reaches the program as one
-* `argv` element, whatever it contains.
-*/
-/** Long enough for a cold image build; short enough that a hung one ends. */
-const DEFAULT_TIMEOUT_MS = 18e5;
-/** How long a timed-out child has to exit on SIGTERM before it is killed. */
-const KILL_GRACE_MS = 5e3;
-/** The command line as a person would read it — for messages, never to run. */
-function display(command, args) {
-	return [command, ...args].join(" ");
-}
-/** The program ran and exited unsuccessfully; its own output said why. */
-var CommandFailed = class extends Error {
-	command;
-	args;
-	exitCode;
-	signal;
-	constructor(command, args, exitCode, signal) {
-		super(`\`${display(command, args)}\` ${exitCode === null ? `was stopped by ${signal ?? "a signal"}` : `exited with code ${exitCode}`}. Its output above says why; run it by hand to see it again.`);
-		this.command = command;
-		this.args = args;
-		this.exitCode = exitCode;
-		this.signal = signal;
-		this.name = "CommandFailed";
-	}
-};
-/** The program ran past its timeout and was killed. */
-var CommandTimedOut = class extends Error {
-	command;
-	args;
-	timeoutMs;
-	constructor(command, args, timeoutMs) {
-		super(`\`${display(command, args)}\` was still running after ${Math.round(timeoutMs / 1e3)}s and was stopped. Check what it was waiting on — a registry, the Docker daemon, a prompt — and run it again.`);
-		this.command = command;
-		this.args = args;
-		this.timeoutMs = timeoutMs;
-		this.name = "CommandTimedOut";
-	}
-};
-/**
-* Run `command` with `args`, resolving when it exits 0.
-*
-* Rejects with {@link CommandFailed} on any other exit, {@link CommandTimedOut}
-* once `timeoutMs` passes (after the child is gone), and with the spawn error
-* itself when the program cannot be started at all — `ENOENT` already names it.
-*/
-async function run(command, args, options = {}) {
-	await spawnChild(command, args, options, false);
-}
-/**
-* {@link run}, resolving with what the program wrote to stdout — for a value
-* the CLI reads back, such as the digest `docker inspect` reports. stderr still
-* reaches the terminal, so a failure explains itself the same way.
-*/
-function runOutput(command, args, options = {}) {
-	return spawnChild(command, args, options, true);
-}
-function spawnChild(command, args, options, capture) {
-	const { timeoutMs = DEFAULT_TIMEOUT_MS, ...spawnOptions } = options;
-	return new Promise((resolve, reject) => {
-		const child = (0, node_child_process.spawn)(command, [...args], {
-			stdio: "inherit",
-			...spawnOptions,
-			...capture ? { stdio: [
-				"ignore",
-				"pipe",
-				"inherit"
-			] } : {},
-			shell: false
-		});
-		let stdout = "";
-		child.stdout?.on("data", (chunk) => {
-			stdout += chunk.toString();
-		});
-		let timedOut = false;
-		let killer;
-		const timer = setTimeout(() => {
-			timedOut = true;
-			child.kill("SIGTERM");
-			killer = setTimeout(() => child.kill("SIGKILL"), KILL_GRACE_MS);
-			killer.unref?.();
-		}, timeoutMs);
-		timer.unref?.();
-		const settle = () => {
-			clearTimeout(timer);
-			if (killer) clearTimeout(killer);
-		};
-		child.on("error", (error) => {
-			settle();
-			reject(spawnOptions.signal?.aborted ? spawnOptions.signal.reason : error);
-		});
-		child.on("close", (code, signal) => {
-			settle();
-			if (spawnOptions.signal?.aborted) reject(spawnOptions.signal.reason);
-			else if (timedOut) reject(new CommandTimedOut(command, args, timeoutMs));
-			else if (code === 0) resolve(stdout);
-			else reject(new CommandFailed(command, args, code, signal));
-		});
-	});
-}
-//#endregion
-Object.defineProperty(exports, "CommandFailed", {
-	enumerable: true,
-	get: function() {
-		return CommandFailed;
-	}
-});
-Object.defineProperty(exports, "CommandTimedOut", {
-	enumerable: true,
-	get: function() {
-		return CommandTimedOut;
-	}
-});
-Object.defineProperty(exports, "DEFAULT_TIMEOUT_MS", {
-	enumerable: true,
-	get: function() {
-		return DEFAULT_TIMEOUT_MS;
-	}
-});
-Object.defineProperty(exports, "GKM_HOME_ENV", {
-	enumerable: true,
-	get: function() {
-		return GKM_HOME_ENV;
-	}
-});
-Object.defineProperty(exports, "gkmHome", {
-	enumerable: true,
-	get: function() {
-		return gkmHome;
-	}
-});
-Object.defineProperty(exports, "run", {
-	enumerable: true,
-	get: function() {
-		return run;
-	}
-});
-Object.defineProperty(exports, "runOutput", {
-	enumerable: true,
-	get: function() {
-		return runOutput;
-	}
-});
-
-//# sourceMappingURL=run-fVZ-rLnc.cjs.map

package/dist/run-fVZ-rLnc.cjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"run-fVZ-rLnc.cjs","names":["resolve","join","homedir","spawn"],"sources":["../src/home.ts","../src/run.ts"],"sourcesContent":["/**\n * Where the CLI keeps what belongs to a person rather than a project: stage\n * keys and stored provider credentials.\n *\n * `GKM_HOME` names it, so a CI job, a shared build runner or a test can give\n * every run its own instead of reaching into whoever's home directory the\n * process happens to have. Unset, it is `~/.gkm`, where it has always been.\n */\n\nimport { homedir } from 'node:os';\nimport { join, resolve } from 'node:path';\n\n/** The environment variable that moves the CLI's home. */\nexport const GKM_HOME_ENV = 'GKM_HOME';\n\n/** The CLI's home: `GKM_HOME` if set, else `~/.gkm`. */\nexport function gkmHome(env: NodeJS.ProcessEnv = process.env): string {\n\tconst configured = env[GKM_HOME_ENV];\n\treturn configured ? resolve(configured) : join(homedir(), '.gkm');\n}\n","/**\n * Start a program with an argument array, never a shell string.\n *\n * `gkm build`, `gkm docker` and `gkm deploy` pass values that come from the\n * workspace — image refs, tags, build args, package names — to `docker` and\n * `turbo`. Joined into a string and handed to a shell, a package named\n * `x;curl …|sh` or a tag holding `$(…)` became part of the command line, which\n * matters most where the CLI builds a repository it didn't write: a CI job for a\n * fork, a shared build runner. Here every value reaches the program as one\n * `argv` element, whatever it contains.\n */\n\nimport { type SpawnOptions, spawn } from 'node:child_process';\n\n/** Long enough for a cold image build; short enough that a hung one ends. */\nexport const DEFAULT_TIMEOUT_MS = 30 * 60_000;\n\n/** How long a timed-out child has to exit on SIGTERM before it is killed. */\nconst KILL_GRACE_MS = 5_000;\n\nexport interface RunOptions {\n\tcwd?: string;\n\tenv?: NodeJS.ProcessEnv;\n\tstdio?: SpawnOptions['stdio'];\n\t/** Kill the child after this long. Defaults to {@link DEFAULT_TIMEOUT_MS}. */\n\ttimeoutMs?: number;\n\t/**\n\t * Kills the child when aborted, and rejects with the signal's reason — the\n\t * same as a stopped deploy's other calls.\n\t */\n\tsignal?: AbortSignal;\n}\n\n/** The command line as a person would read it — for messages, never to run. */\nfunction display(command: string, args: readonly string[]): string {\n\treturn [command, ...args].join(' ');\n}\n\n/** The program ran and exited unsuccessfully; its own output said why. */\nexport class CommandFailed extends Error {\n\tconstructor(\n\t\treadonly command: string,\n\t\treadonly args: readonly string[],\n\t\treadonly exitCode: number | null,\n\t\treadonly signal: NodeJS.Signals | null,\n\t) {\n\t\tsuper(\n\t\t\t`\\`${display(command, args)}\\` ${exitCode === null ? `was stopped by ${signal ?? 'a signal'}` : `exited with code ${exitCode}`}. Its output above says why; run it by hand to see it again.`,\n\t\t);\n\t\tthis.name = 'CommandFailed';\n\t}\n}\n\n/** The program ran past its timeout and was killed. */\nexport class CommandTimedOut extends Error {\n\tconstructor(\n\t\treadonly command: string,\n\t\treadonly args: readonly string[],\n\t\treadonly timeoutMs: number,\n\t) {\n\t\tsuper(\n\t\t\t`\\`${display(command, args)}\\` was still running after ${Math.round(timeoutMs / 1000)}s and was stopped. Check what it was waiting on — a registry, the Docker daemon, a prompt — and run it again.`,\n\t\t);\n\t\tthis.name = 'CommandTimedOut';\n\t}\n}\n\n/**\n * Run `command` with `args`, resolving when it exits 0.\n *\n * Rejects with {@link CommandFailed} on any other exit, {@link CommandTimedOut}\n * once `timeoutMs` passes (after the child is gone), and with the spawn error\n * itself when the program cannot be started at all — `ENOENT` already names it.\n */\nexport async function run(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: RunOptions = {},\n): Promise<void> {\n\tawait spawnChild(command, args, options, false);\n}\n\n/**\n * {@link run}, resolving with what the program wrote to stdout — for a value\n * the CLI reads back, such as the digest `docker inspect` reports. stderr still\n * reaches the terminal, so a failure explains itself the same way.\n */\nexport function runOutput(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: Omit<RunOptions, 'stdio'> = {},\n): Promise<string> {\n\treturn spawnChild(command, args, options, true);\n}\n\nfunction spawnChild(\n\tcommand: string,\n\targs: readonly string[],\n\toptions: RunOptions,\n\tcapture: boolean,\n): Promise<string> {\n\tconst { timeoutMs = DEFAULT_TIMEOUT_MS, ...spawnOptions } = options;\n\n\treturn new Promise<string>((resolve, reject) => {\n\t\tconst child = spawn(command, [...args], {\n\t\t\tstdio: 'inherit',\n\t\t\t...spawnOptions,\n\t\t\t...(capture ? { stdio: ['ignore', 'pipe', 'inherit'] } : {}),\n\t\t\tshell: false,\n\t\t});\n\n\t\tlet stdout = '';\n\t\tchild.stdout?.on('data', (chunk: Buffer) => {\n\t\t\tstdout += chunk.toString();\n\t\t});\n\n\t\tlet timedOut = false;\n\t\tlet killer: NodeJS.Timeout | undefined;\n\t\tconst timer = setTimeout(() => {\n\t\t\ttimedOut = true;\n\t\t\tchild.kill('SIGTERM');\n\t\t\t// A child that ignores SIGTERM would hold the deploy open forever.\n\t\t\tkiller = setTimeout(() => child.kill('SIGKILL'), KILL_GRACE_MS);\n\t\t\tkiller.unref?.();\n\t\t}, timeoutMs);\n\t\ttimer.unref?.();\n\n\t\tconst settle = () => {\n\t\t\tclearTimeout(timer);\n\t\t\tif (killer) clearTimeout(killer);\n\t\t};\n\n\t\tchild.on('error', (error) => {\n\t\t\tsettle();\n\t\t\t// Node reports an abort as its own `AbortError`; the caller asked\n\t\t\t// with a reason, and that is what it should get back.\n\t\t\treject(spawnOptions.signal?.aborted ? spawnOptions.signal.reason : error);\n\t\t});\n\n\t\tchild.on('close', (code: number | null, signal: NodeJS.Signals | null) => {\n\t\t\tsettle();\n\t\t\tif (spawnOptions.signal?.aborted) reject(spawnOptions.signal.reason);\n\t\t\telse if (timedOut) reject(new CommandTimedOut(command, args, timeoutMs));\n\t\t\telse if (code === 0) resolve(stdout);\n\t\t\telse reject(new CommandFailed(command, args, code, signal));\n\t\t});\n\t});\n}\n"],"mappings":";;;;;;;;;;;;;AAaA,MAAa,eAAe;;AAG5B,SAAgB,QAAQ,MAAyB,QAAQ,KAAa;CACrE,MAAM,aAAa,IAAI;CACvB,OAAO,cAAA,GAAaA,UAAAA,QAAAA,CAAQ,UAAU,KAAA,GAAIC,UAAAA,KAAAA,EAAAA,GAAKC,QAAAA,QAAAA,CAAQ,GAAG,MAAM;AACjE;;;;;;;;;;;;;;;ACJA,MAAa,qBAAqB;;AAGlC,MAAM,gBAAgB;;AAgBtB,SAAS,QAAQ,SAAiB,MAAiC;CAClE,OAAO,CAAC,SAAS,GAAG,IAAI,CAAC,CAAC,KAAK,GAAG;AACnC;;AAGA,IAAa,gBAAb,cAAmC,MAAM;CAE9B;CACA;CACA;CACA;CAJV,YACC,SACA,MACA,UACA,QACC;EACD,MACC,KAAK,QAAQ,SAAS,IAAI,EAAE,KAAK,aAAa,OAAO,kBAAkB,UAAU,eAAe,oBAAoB,WAAW,6DAChI;EAPS,KAAA,UAAA;EACA,KAAA,OAAA;EACA,KAAA,WAAA;EACA,KAAA,SAAA;EAKT,KAAK,OAAO;CACb;AACD;;AAGA,IAAa,kBAAb,cAAqC,MAAM;CAEhC;CACA;CACA;CAHV,YACC,SACA,MACA,WACC;EACD,MACC,KAAK,QAAQ,SAAS,IAAI,EAAE,6BAA6B,KAAK,MAAM,YAAY,GAAI,EAAE,8GACvF;EANS,KAAA,UAAA;EACA,KAAA,OAAA;EACA,KAAA,YAAA;EAKT,KAAK,OAAO;CACb;AACD;;;;;;;;AASA,eAAsB,IACrB,SACA,MACA,UAAsB,CAAC,GACP;CAChB,MAAM,WAAW,SAAS,MAAM,SAAS,KAAK;AAC/C;;;;;;AAOA,SAAgB,UACf,SACA,MACA,UAAqC,CAAC,GACpB;CAClB,OAAO,WAAW,SAAS,MAAM,SAAS,IAAI;AAC/C;AAEA,SAAS,WACR,SACA,MACA,SACA,SACkB;CAClB,MAAM,EAAE,YAAY,oBAAoB,GAAG,iBAAiB;CAE5D,OAAO,IAAI,SAAiB,SAAS,WAAW;EAC/C,MAAM,SAAA,GAAQC,mBAAAA,MAAAA,CAAM,SAAS,CAAC,GAAG,IAAI,GAAG;GACvC,OAAO;GACP,GAAG;GACH,GAAI,UAAU,EAAE,OAAO;IAAC;IAAU;IAAQ;GAAS,EAAE,IAAI,CAAC;GAC1D,OAAO;EACR,CAAC;EAED,IAAI,SAAS;EACb,MAAM,QAAQ,GAAG,SAAS,UAAkB;GAC3C,UAAU,MAAM,SAAS;EAC1B,CAAC;EAED,IAAI,WAAW;EACf,IAAI;EACJ,MAAM,QAAQ,iBAAiB;GAC9B,WAAW;GACX,MAAM,KAAK,SAAS;GAEpB,SAAS,iBAAiB,MAAM,KAAK,SAAS,GAAG,aAAa;GAC9D,OAAO,QAAQ;EAChB,GAAG,SAAS;EACZ,MAAM,QAAQ;EAEd,MAAM,eAAe;GACpB,aAAa,KAAK;GAClB,IAAI,QAAQ,aAAa,MAAM;EAChC;EAEA,MAAM,GAAG,UAAU,UAAU;GAC5B,OAAO;GAGP,OAAO,aAAa,QAAQ,UAAU,aAAa,OAAO,SAAS,KAAK;EACzE,CAAC;EAED,MAAM,GAAG,UAAU,MAAqB,WAAkC;GACzE,OAAO;GACP,IAAI,aAAa,QAAQ,SAAS,OAAO,aAAa,OAAO,MAAM;QAC9D,IAAI,UAAU,OAAO,IAAI,gBAAgB,SAAS,MAAM,SAAS,CAAC;QAClE,IAAI,SAAS,GAAG,QAAQ,MAAM;QAC9B,OAAO,IAAI,cAAc,SAAS,MAAM,MAAM,MAAM,CAAC;EAC3D,CAAC;CACF,CAAC;AACF"}

package/dist/sandbox-C4g1eG31.d.mts

@@ -1,104 +0,0 @@
-import { jt as GkmError } from "./types-HqVPddRK.mjs";
-//#region src/sandbox/sandbox.d.ts
-/** Where a command's output goes. */
-type SandboxOutput = 'capture' | 'inherit' | 'stderr' | 'ignore';
-interface SandboxExecOptions {
-  /**
-   * Where the command runs: the project root or a directory below it, as an
-   * absolute path or relative to the root. Anywhere else is refused with
-   * {@link SandboxCwdEscape}.
-   */
-  cwd: string;
-  /**
-   * The command's whole environment. Nothing of the host's is added to it:
-   * start from {@link Sandbox.env} and add what the step needs.
-   */
-  env: Readonly<Record<string, string>>;
-  /**
-   * How long the command may run before it is killed. Required: a step that
-   * waits forever — a sniffed entry that opens a server, a build stuck on a
-   * prompt — would otherwise hold the deploy, and its lock, forever.
-   */
-  timeoutMs: number;
-  /**
-   * Files the command can read, by name. Mounted in a directory of their own
-   * — named by `GKM_SECRETS_DIR` in the command's environment — and removed
-   * when it exits. Never set as variables, which every child inherits, a
-   * crash report prints and `/proc/<pid>/environ` shows.
-   */
-  secrets?: Readonly<Record<string, string>>;
-  /**
-   * `capture` (the default) returns stdout and stderr in the result;
-   * `inherit` gives the command the host's terminal; `stderr` sends both
-   * streams to the host's stderr; `ignore` discards them.
-   */
-  output?: SandboxOutput;
-  /** Kills the command when aborted; `exec` rejects with the signal's reason. */
-  signal?: AbortSignal;
-}
-/** How a command ended. A non-zero exit is a result, not an error. */
-interface SandboxResult {
-  exitCode: number | null;
-  signal: string | null;
-  /** What it wrote to stdout, when its output was captured. */
-  stdout: string;
-  /** What it wrote to stderr, when its output was captured. */
-  stderr: string;
-}
-/**
- * Runs a command against the project, and nothing else of the host's.
- *
- * `exec` resolves with the result however the command exited. It rejects
- * with {@link CommandTimedOut} once the timeout passes — after the command is
- * gone — with {@link SandboxCwdEscape} for a directory outside the project,
- * with the signal's reason when aborted, and with the spawn error when the
- * program cannot be started.
- */
-interface Sandbox {
-  /** The project: the directory every command runs at or below. */
-  readonly root: string;
-  /**
-   * Whether the code it runs is kept from the host: its files, its
-   * processes, its memory.
-   *
-   * An isolating sandbox shares nothing but what crosses `exec`, so a config
-   * reaches the deploy as data — a live object in it (a custom state store,
-   * an inline target) cannot cross, and is refused with
-   * `ConfigObjectNotSerializable`. A non-isolating one, like
-   * {@link LocalSandbox}, runs on the host as the host's user; a project
-   * whose config holds live objects is then loaded in-process as before,
-   * because a project trusted to run there is trusted to do that.
-   */
-  readonly isolating: boolean;
-  /**
-   * The environment a command starts from: what any program needs to run
-   * here — `PATH`, `HOME`, the locale — and no credential.
-   */
-  readonly env: Readonly<Record<string, string>>;
-  exec(command: string, args: readonly string[], options: SandboxExecOptions): Promise<SandboxResult>;
-}
-/** The variable naming the directory a command's secrets are mounted in. */
-declare const SECRETS_DIR_ENV = "GKM_SECRETS_DIR";
-/** A command was asked to run outside the project. */
-declare class SandboxCwdEscape extends GkmError {
-  readonly cwd: string;
-  readonly root: string;
-  constructor(cwd: string, root: string);
-}
-/**
- * `cwd` as an absolute directory inside `root`, or {@link SandboxCwdEscape}.
- *
- * Symlinks are resolved on both sides first, so a link inside the project
- * that points out of it is an escape, and a project reached through a link
- * (`/tmp` on macOS) is still itself. For a sandbox of a host's own to call
- * before it runs anything.
- */
-declare function confineCwd(root: string, cwd: string): string;
-/** A secret's file name: one path segment, so it cannot be written elsewhere. */
-declare class SecretNameInvalid extends GkmError {
-  readonly secretName: string;
-  constructor(secretName: string);
-}
-//#endregion
-export { SandboxOutput as a, confineCwd as c, SandboxExecOptions as i, Sandbox as n, SandboxResult as o, SandboxCwdEscape as r, SecretNameInvalid as s, SECRETS_DIR_ENV as t };
-//# sourceMappingURL=sandbox-C4g1eG31.d.mts.map

package/dist/sandbox-C4g1eG31.d.mts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sandbox-C4g1eG31.d.mts","names":[],"sources":["../src/sandbox/sandbox.ts"],"mappings":";;;KA8BY;UAEK;;;;;;EAMhB;;;;;EAKA,KAAK,SAAS;;;;;;EAMd;;;;;;;EAOA,UAAU,SAAS;;;;;;EAMnB,SAAS;;EAET,SAAS;;;UAIO;EAChB;EACA;;EAEA;;EAEA;;;;;;;;;;;UAYgB;;WAEP;;;;;;;;;;;;;WAaA;;;;;WAKA,KAAK,SAAS;EACvB,KACC,iBACA,yBACA,SAAS,qBACP,QAAQ;;;cAIC;;cAGA,yBAAyB;WAE3B;WACA;EAFV,YACU,aACA;;;;;;;;;;iBAwBK,WAAW,cAAc;;cAU5B,0BAA0B;WACjB;EAArB,YAAqB"}

package/dist/sandbox-CdKgQ3XU.d.cts

@@ -1,104 +0,0 @@
-import { jt as GkmError } from "./types-B6UXlEkf.cjs";
-//#region src/sandbox/sandbox.d.ts
-/** Where a command's output goes. */
-type SandboxOutput = 'capture' | 'inherit' | 'stderr' | 'ignore';
-interface SandboxExecOptions {
-  /**
-   * Where the command runs: the project root or a directory below it, as an
-   * absolute path or relative to the root. Anywhere else is refused with
-   * {@link SandboxCwdEscape}.
-   */
-  cwd: string;
-  /**
-   * The command's whole environment. Nothing of the host's is added to it:
-   * start from {@link Sandbox.env} and add what the step needs.
-   */
-  env: Readonly<Record<string, string>>;
-  /**
-   * How long the command may run before it is killed. Required: a step that
-   * waits forever — a sniffed entry that opens a server, a build stuck on a
-   * prompt — would otherwise hold the deploy, and its lock, forever.
-   */
-  timeoutMs: number;
-  /**
-   * Files the command can read, by name. Mounted in a directory of their own
-   * — named by `GKM_SECRETS_DIR` in the command's environment — and removed
-   * when it exits. Never set as variables, which every child inherits, a
-   * crash report prints and `/proc/<pid>/environ` shows.
-   */
-  secrets?: Readonly<Record<string, string>>;
-  /**
-   * `capture` (the default) returns stdout and stderr in the result;
-   * `inherit` gives the command the host's terminal; `stderr` sends both
-   * streams to the host's stderr; `ignore` discards them.
-   */
-  output?: SandboxOutput;
-  /** Kills the command when aborted; `exec` rejects with the signal's reason. */
-  signal?: AbortSignal;
-}
-/** How a command ended. A non-zero exit is a result, not an error. */
-interface SandboxResult {
-  exitCode: number | null;
-  signal: string | null;
-  /** What it wrote to stdout, when its output was captured. */
-  stdout: string;
-  /** What it wrote to stderr, when its output was captured. */
-  stderr: string;
-}
-/**
- * Runs a command against the project, and nothing else of the host's.
- *
- * `exec` resolves with the result however the command exited. It rejects
- * with {@link CommandTimedOut} once the timeout passes — after the command is
- * gone — with {@link SandboxCwdEscape} for a directory outside the project,
- * with the signal's reason when aborted, and with the spawn error when the
- * program cannot be started.
- */
-interface Sandbox {
-  /** The project: the directory every command runs at or below. */
-  readonly root: string;
-  /**
-   * Whether the code it runs is kept from the host: its files, its
-   * processes, its memory.
-   *
-   * An isolating sandbox shares nothing but what crosses `exec`, so a config
-   * reaches the deploy as data — a live object in it (a custom state store,
-   * an inline target) cannot cross, and is refused with
-   * `ConfigObjectNotSerializable`. A non-isolating one, like
-   * {@link LocalSandbox}, runs on the host as the host's user; a project
-   * whose config holds live objects is then loaded in-process as before,
-   * because a project trusted to run there is trusted to do that.
-   */
-  readonly isolating: boolean;
-  /**
-   * The environment a command starts from: what any program needs to run
-   * here — `PATH`, `HOME`, the locale — and no credential.
-   */
-  readonly env: Readonly<Record<string, string>>;
-  exec(command: string, args: readonly string[], options: SandboxExecOptions): Promise<SandboxResult>;
-}
-/** The variable naming the directory a command's secrets are mounted in. */
-declare const SECRETS_DIR_ENV = "GKM_SECRETS_DIR";
-/** A command was asked to run outside the project. */
-declare class SandboxCwdEscape extends GkmError {
-  readonly cwd: string;
-  readonly root: string;
-  constructor(cwd: string, root: string);
-}
-/**
- * `cwd` as an absolute directory inside `root`, or {@link SandboxCwdEscape}.
- *
- * Symlinks are resolved on both sides first, so a link inside the project
- * that points out of it is an escape, and a project reached through a link
- * (`/tmp` on macOS) is still itself. For a sandbox of a host's own to call
- * before it runs anything.
- */
-declare function confineCwd(root: string, cwd: string): string;
-/** A secret's file name: one path segment, so it cannot be written elsewhere. */
-declare class SecretNameInvalid extends GkmError {
-  readonly secretName: string;
-  constructor(secretName: string);
-}
-//#endregion
-export { SandboxOutput as a, confineCwd as c, SandboxExecOptions as i, Sandbox as n, SandboxResult as o, SandboxCwdEscape as r, SecretNameInvalid as s, SECRETS_DIR_ENV as t };
-//# sourceMappingURL=sandbox-CdKgQ3XU.d.cts.map

package/dist/sandbox-CdKgQ3XU.d.cts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sandbox-CdKgQ3XU.d.cts","names":[],"sources":["../src/sandbox/sandbox.ts"],"mappings":";;;KA8BY;UAEK;;;;;;EAMhB;;;;;EAKA,KAAK,SAAS;;;;;;EAMd;;;;;;;EAOA,UAAU,SAAS;;;;;;EAMnB,SAAS;;EAET,SAAS;;;UAIO;EAChB;EACA;;EAEA;;EAEA;;;;;;;;;;;UAYgB;;WAEP;;;;;;;;;;;;;WAaA;;;;;WAKA,KAAK,SAAS;EACvB,KACC,iBACA,yBACA,SAAS,qBACP,QAAQ;;;cAIC;;cAGA,yBAAyB;WAE3B;WACA;EAFV,YACU,aACA;;;;;;;;;;iBAwBK,WAAW,cAAc;;cAU5B,0BAA0B;WACjB;EAArB,YAAqB"}