neon 2.47.0 → 3.1.0

package/dist/pkg.js

@@ -1,25 +1,23 @@
 import { readFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
+//#region src/pkg.ts
 /**
- * Load the CLI's package.json for version metadata. In the built CLI it sits right next to
- * this module (the build copies it into `dist`); when running from source (tests, `tsx`) it
- * does not, so we walk up to the nearest `package.json`. Both layouts resolve to the same
- * file, keeping `pkg.version` correct everywhere without a test-only shim.
- */
+* Load the CLI's package.json for version metadata. In the built CLI it sits right next to
+* this module (the build copies it into `dist`); when running from source (tests, `tsx`) it
+* does not, so we walk up to the nearest `package.json`. Both layouts resolve to the same
+* file, keeping `pkg.version` correct everywhere without a test-only shim.
+*/
 const loadPkg = () => {
-    let dir = dirname(fileURLToPath(import.meta.url));
-    for (;;) {
-        try {
-            return JSON.parse(readFileSync(join(dir, "package.json"), "utf-8"));
-        }
-        catch {
-            const parent = dirname(dir);
-            if (parent === dir) {
-                throw new Error("Could not locate package.json for version detection.");
-            }
-            dir = parent;
-        }
-    }
+	let dir = dirname(fileURLToPath(import.meta.url));
+	for (;;) try {
+		return JSON.parse(readFileSync(join(dir, "package.json"), "utf-8"));
+	} catch {
+		const parent = dirname(dir);
+		if (parent === dir) throw new Error("Could not locate package.json for version detection.");
+		dir = parent;
+	}
 };
-export default loadPkg();
+var pkg_default = loadPkg();
+//#endregion
+export { pkg_default as default };

package/dist/profile_keys.js

@@ -1,55 +1,52 @@
-/**
- * Helpers for the API-key half of a profile: naming a minted key, reading one off disk, and
- * turning what the API says about a key into something displayable.
- *
- * Kept apart from `./commands/profile.ts` because these are the decisions worth testing
- * directly — the command around them is prompts, an API client, and output.
- */
 import { randomBytes } from "node:crypto";
+//#region src/profile_keys.ts
+/**
+* Helpers for the API-key half of a profile: naming a minted key, reading one off disk, and
+* turning what the API says about a key into something displayable.
+*
+* Kept apart from `./commands/profile.ts` because these are the decisions worth testing
+* directly — the command around them is prompts, an API client, and output.
+*/
 /** Auth methods that are an API key. Anything else is not a key and must not be stored as one. */
 const API_KEY_METHODS = ["api_key_user", "api_key_org"];
-export const isApiKeyMethod = (method) => API_KEY_METHODS.includes(method);
+const isApiKeyMethod = (method) => API_KEY_METHODS.includes(method);
 /**
- * A unique name for a key we mint, carrying the profile it belongs to, a UTC timestamp, and a
- * random suffix.
- *
- * Neither part is decoration. Key names are unique per account and the key being replaced still
- * holds its name while the replacement is minted, so a stable name fails the rotation outright
- * with `choose another unique name for api key`.
- *
- * The random suffix is there because a timestamp alone is not enough: at second precision two
- * rotations in the same second collide, which is easy to hit from a script and was hit while
- * testing this. Going to milliseconds only narrows the window, so the name carries four random
- * hex characters and the class of failure is gone rather than made less likely.
- */
-export const mintedKeyName = (profile, now = new Date(), suffix = randomBytes(2).toString("hex")) => {
-    const stamp = now
-        .toISOString()
-        .replace(/[-:]/g, "")
-        .replace(/\.\d+Z$/, "Z");
-    return `neon-cli-${profile}-${stamp}-${suffix}`;
+* A unique name for a key we mint, carrying the profile it belongs to, a UTC timestamp, and a
+* random suffix.
+*
+* Neither part is decoration. Key names are unique per account and the key being replaced still
+* holds its name while the replacement is minted, so a stable name fails the rotation outright
+* with `choose another unique name for api key`.
+*
+* The random suffix is there because a timestamp alone is not enough: at second precision two
+* rotations in the same second collide, which is easy to hit from a script and was hit while
+* testing this. Going to milliseconds only narrows the window, so the name carries four random
+* hex characters and the class of failure is gone rather than made less likely.
+*/
+const mintedKeyName = (profile, now = /* @__PURE__ */ new Date(), suffix = randomBytes(2).toString("hex")) => {
+	return `neon-cli-${profile}-${now.toISOString().replace(/[-:]/g, "").replace(/\.\d+Z$/, "Z")}-${suffix}`;
 };
 /**
- * What to record about a validated key.
- *
- * An organization-scoped key has no user, and `GET /users/me` answers `404 not allowed for
- * organization API keys` — so the account id is the only identity available, and asking for an
- * email would turn a perfectly good key into a failed `profile create`. The id is returned bare
- * rather than as "organization <id>": it already announces what it is through its `org-` prefix,
- * and `list` shows the scope in the next column.
- */
-export const identityFromAuthDetails = (details, email) => {
-    if (details.auth_method === "api_key_org") {
-        return { label: details.account_id };
-    }
-    return {
-        ...(email ? { label: email } : { label: details.account_id }),
-        ...(details.account_id ? { userId: details.account_id } : {}),
-    };
+* What to record about a validated key.
+*
+* An organization-scoped key has no user, and `GET /users/me` answers `404 not allowed for
+* organization API keys` — so the account id is the only identity available, and asking for an
+* email would turn a perfectly good key into a failed `profile create`. The id is returned bare
+* rather than as "organization <id>": it already announces what it is through its `org-` prefix,
+* and `list` shows the scope in the next column.
+*/
+const identityFromAuthDetails = (details, email) => {
+	if (details.auth_method === "api_key_org") return { label: details.account_id };
+	return {
+		...email ? { label: email } : { label: details.account_id },
+		...details.account_id ? { userId: details.account_id } : {}
+	};
 };
 /**
- * The message for a credential that authenticates but is not an API key — an OAuth access
- * token pasted in by mistake, most likely. It would work until it expired, then fail with no
- * way to refresh it, so it is refused at the point where the mistake is still obvious.
- */
-export const notAnApiKeyMessage = (method) => `That credential authenticates as "${method}", not an API key. Create a key with \`neon api-keys create --name <name>\`, or have one minted with \`neon profile create <name> --mint\`.`;
+* The message for a credential that authenticates but is not an API key — an OAuth access
+* token pasted in by mistake, most likely. It would work until it expired, then fail with no
+* way to refresh it, so it is refused at the point where the mistake is still obvious.
+*/
+const notAnApiKeyMessage = (method) => `That credential authenticates as "${method}", not an API key. Create a key with \`neon api-keys create --name <name>\`, or have one minted with \`neon profile create <name> --mint\`.`;
+//#endregion
+export { identityFromAuthDetails, isApiKeyMethod, mintedKeyName, notAnApiKeyMessage };

package/dist/psql/cli.js

@@ -1,53 +1,50 @@
 #!/usr/bin/env node
-/**
- * Standalone psql shim.
- *
- * Thin wrapper around `runPsql` that lets the conformance harness — and any
- * caller that wants a psql-compatible CLI — invoke our embedded TypeScript
- * psql directly via `node dist/psql/cli.js`, without going through the
- * neonctl yargs entrypoint.
- *
- * Why this exists: `dist/cli.js` is the neonctl entrypoint; yargs eats
- * libpq-style flags (e.g. `-v ON_ERROR_STOP=0` collides with yargs'
- * built-in `--version`). The conformance suite needs to spawn a binary
- * that accepts the upstream psql flag grammar (`-h`/`-p`/`-U`/`-d`/`-X`/
- * `-v VAR=VALUE`/`--no-psqlrc`/`--echo-all`/`--quiet`/etc.) and reads SQL
- * from stdin. This shim wires `process.argv.slice(2)` straight into
- * `runPsql`, which already speaks that grammar via `parseStartupArgs`.
- *
- * Argv shape:
- *   - If the first positional looks like a connection URI / conninfo
- *     (per `looksLikeConnectionString`), it stays at argv[0] — same shape
- *     as the legacy native-psql call site in `src/utils/psql.ts` and the
- *     existing `runPsql` API.
- *   - Otherwise (the regress harness case: bare libpq flags), we prepend
- *     an empty placeholder URI so `runPsql([''] + flags)` falls through to
- *     `parseStartupArgs` and resolves the connection from `-h`/`-p`/`-U`/
- *     `-d` plus PG* env / pgpass / service via the layered resolver.
- *
- * Exit code: forwarded straight from `runPsql` (matches upstream psql's
- * EXIT_SUCCESS / EXIT_FAILURE / EXIT_USER / EXIT_BADCONN values; see
- * `core/mainloop.ts`).
- */
 import { looksLikeConnectionString, runPsql } from "./index.js";
+//#region src/psql/cli.ts
+/**
+* Standalone psql shim.
+*
+* Thin wrapper around `runPsql` that lets the conformance harness — and any
+* caller that wants a psql-compatible CLI — invoke our embedded TypeScript
+* psql directly via `node dist/psql/cli.js`, without going through the
+* neonctl yargs entrypoint.
+*
+* Why this exists: `dist/cli.js` is the neonctl entrypoint; yargs eats
+* libpq-style flags (e.g. `-v ON_ERROR_STOP=0` collides with yargs'
+* built-in `--version`). The conformance suite needs to spawn a binary
+* that accepts the upstream psql flag grammar (`-h`/`-p`/`-U`/`-d`/`-X`/
+* `-v VAR=VALUE`/`--no-psqlrc`/`--echo-all`/`--quiet`/etc.) and reads SQL
+* from stdin. This shim wires `process.argv.slice(2)` straight into
+* `runPsql`, which already speaks that grammar via `parseStartupArgs`.
+*
+* Argv shape:
+*   - If the first positional looks like a connection URI / conninfo
+*     (per `looksLikeConnectionString`), it stays at argv[0] — same shape
+*     as the legacy native-psql call site in `src/utils/psql.ts` and the
+*     existing `runPsql` API.
+*   - Otherwise (the regress harness case: bare libpq flags), we prepend
+*     an empty placeholder URI so `runPsql([''] + flags)` falls through to
+*     `parseStartupArgs` and resolves the connection from `-h`/`-p`/`-U`/
+*     `-d` plus PG* env / pgpass / service via the layered resolver.
+*
+* Exit code: forwarded straight from `runPsql` (matches upstream psql's
+* EXIT_SUCCESS / EXIT_FAILURE / EXIT_USER / EXIT_BADCONN values; see
+* `core/mainloop.ts`).
+*/
 const main = async () => {
-    const raw = process.argv.slice(2);
-    // Detect whether the first arg is a connection URI/conninfo string.
-    // libpq's `recognized_connection_string()` covers both `postgres[ql]://…`
-    // URIs and bare `key=value` conninfo strings — `looksLikeConnectionString`
-    // mirrors that test.
-    const argv = raw.length > 0 && looksLikeConnectionString(raw[0])
-        ? raw
-        : ["", ...raw];
-    const code = await runPsql(argv, {
-        stdin: process.stdin,
-        stdout: process.stdout,
-        stderr: process.stderr,
-    });
-    process.exit(code);
+	const raw = process.argv.slice(2);
+	const argv = raw.length > 0 && looksLikeConnectionString(raw[0]) ? raw : ["", ...raw];
+	const code = await runPsql(argv, {
+		stdin: process.stdin,
+		stdout: process.stdout,
+		stderr: process.stderr
+	});
+	process.exit(code);
 };
 main().catch((err) => {
-    const msg = err instanceof Error ? err.message : String(err);
-    process.stderr.write(`psql: fatal: ${msg}\n`);
-    process.exit(1);
+	const msg = err instanceof Error ? err.message : String(err);
+	process.stderr.write(`psql: fatal: ${msg}\n`);
+	process.exit(1);
 });
+//#endregion
+export {};