neon 5.0.1 → 6.1.0

package/README.md

@@ -46,6 +46,11 @@ brew upgrade neonctl
 
 To upgrade a binary version, download the latest binary file, as described above, and replace your old binary with the new one.
 
+Global npm, pnpm, Bun, and Homebrew installs check for updates once per day.
+When an update is available, terminal commands periodically print the matching
+upgrade command. Set `NO_UPDATE_NOTIFIER=1` to disable these checks. The notifier
+does not run in CI, for machine-readable output, or from standalone binaries.
+
 ## Connect
 
 Run the following command to authenticate a connection to Neon:
@@ -613,6 +618,8 @@ export default defineConfig({
 
 ```
 ? Which Neon services should neon.ts declare? (space to toggle, enter to confirm) ›
+◉   Postgres (always included)
+     Every Neon project includes a Postgres database.
 ◯   Managed Better Auth
      Authentication with users and sessions stored in Postgres.
 ◯   Data API
@@ -625,7 +632,7 @@ export default defineConfig({
      All models, one API, one bill. Powered by Databricks. Not available on the Neon free plan.
 ```
 
-Selecting nothing is a valid answer: you get the starter policy, which is also what a non-interactive run (CI, no TTY) writes. Pass `--services` to skip the prompt anywhere:
+Postgres cannot be unselected. Selecting nothing else is a valid answer: you get the starter policy, which is also what a non-interactive run (CI, no TTY) writes. Pass `--services` to skip the prompt anywhere:
 
 ```bash
 # Pick interactively (TTY) or take the starter policy (CI)
@@ -779,46 +786,42 @@ The target directory must be empty unless you pass `--force` (a lone `.git` is i
 
 ## Set up a project (`init`)
 
-`neon init` sets up this directory for Neon as one flow: agents, a linked project, and optionally `neon.ts`.
+`neon init` sets up coding agents and this directory for Neon. In a terminal it asks **Recommended** or **Custom**. `-y` is Recommended with no prompts. `-y` with `--skill`, MCP flags, `--no-agent-setup`, or `--claimable` is Custom using those flags.
 
-An empty directory (nothing except `.git`) asks how to set up the directory. Pick a starter template, or skip scaffolding and only install agent tooling, link a project, and optionally write `neon.ts`. That skip is only on `init` — `neon bootstrap` always scaffolds.
+Recommended installs the Neon plugin for every detected agent (global config, project folders, and the host CLI). Plugin-capable agents get the plugin; the rest get skills and MCP. If none are detected, it installs the default Neon skills for Cursor and Codex in this directory (`./.agents/skills`) and does not configure MCP. It then links a project when the CLI is authenticated, and writes a default `neon.ts` (Postgres only) using the package manager already in the directory.
 
-`-y` in an empty directory scaffolds the default template (`bootstrap --default`) and does not add a later `config init` step. `--skip-template` skips scaffolding even with `-y`. `--template <id>` scaffolds that template; combine it with `-y` to skip the remaining bootstrap pickers.
+Unauthenticated `-y` skips linking and prints the next step: sign up at https://neon.com/signup, then `neon auth`, `neon link`, or `neon claim create` (no account, expires in 72 hours unless claimed). `-y` never opens a browser. `-y` with `--project-id` or other account flags links when the CLI is already signed in; otherwise it errors and names `neon auth` or `--claimable`.
 
-An existing app (or skip-template) installs agent tooling, then asks whether to link unless `.neon` already has a projectId, then asks whether to create `neon.ts`. Linking uses the same organization, project, and branch flow as `neon link`. Saying no to `neon.ts` skips the services picker and does not write the file. `--no-config` does the same without asking. `-y` writes `config init --services none` unless `--no-config`. `--services` implies creating `neon.ts`.
+Custom asks how to add Neon to coding agents (plugin, skills and MCP separately, or skip), then how to get a project (sign in and link, or a claimable project when you are not signed in), then which services `neon.ts` should declare. Postgres is listed first as always included. The package manager is inferred from the directory; Custom asks only when none is detected. `--skill` selects skills (not the plugin) and skips that picker. MCP flags (`--mcp-config-location`, `--mcp-auth`, `--mcp-project-scoped`) select skills and MCP. `--mcp-config-location` is where the config is written: `global` maps to `neon mcp`, and `project` maps to `neon mcp --project`. With `-y`, the location defaults to `global`; interactive Custom asks. If some selected agents cannot write that location, init warns and skips MCP for those agents while continuing with the supported agents. It fails when none of the selected agents support the location. `--mcp-project-scoped` limits MCP tools to the linked Neon project by passing its ID to `neon mcp --project-id`. Omitted is false, including in Custom; there is no prompt. `--no-agent-setup` skips agent setup.
 
-In an interactive terminal it offers one of: the Neon plugin (`neon plugins`), skills and MCP separately (`neon skills`, then `neon mcp`), or skip agent setup. Agent selection and setup finish before the link question. It never runs plugin and skills+MCP together.
+Empty directories are set up in place. `neon init` does not scaffold starter files.
 
 ```bash
 $ neon init
-$ neon init --skip-template
-$ neon init --skip-template --no-link
 $ neon init -y
-$ neon init --agent cursor --agent claude-code
+$ neon init --agent cursor --agent claude-code --no-link
+$ neon init --no-agent-setup --claimable
+$ neon init -y --skill neon --mcp-auth oauth --mcp-config-location project
+$ neon init -y --agent cursor --project-id <project-id> \
+    --mcp-auth oauth --mcp-config-location project --mcp-project-scoped
 ```
 
-Without a TTY, pass `-y`. `--agent` skips agent selection but does not replace `-y` for link or templates. `--no-link` skips project linking without asking, including when a template is scaffolded.
-
-`-y` skips the template picker and the agent-setup offer. Empty dir: `bootstrap --default`. `--skip-template` or an existing app: plugin when Cursor, Claude Code, or Codex is in project folders, else the host CLI agent; otherwise skills and MCP. If none are found, it exits: pass `--agent <name>`, run from a supported agent, or omit `-y` in a terminal to pick. VS Code, GitHub Copilot CLI, and Grok only take the plugin user-level (`neon plugins --global`), so `-y` uses skills and MCP for those.
-
-`--agent` / `-a` (repeatable) names coding agents and skips agent selection, interactive or with `-y`. Init forwards those names to `plugins`, or to `skills` and `mcp`, not both.
+Without a TTY, pass `-y` or enough flags to answer every question. `-y` alone is Recommended. `-y` with `--skill`, MCP flags, `--no-agent-setup`, or `--claimable` is Custom: those flags, Recommended defaults for the rest. `--skill` selects skills (not the plugin). MCP flags select skills and MCP. `--agent` skips agent selection and, without `-y`, selects Custom. `--no-link` skips project linking without asking. `--no-config` skips `neon.ts`. `--services` implies creating `neon.ts`. `--org-id`, `--project-id`, `--project-name`, `--region-id`, and `--branch` select linking.
 
-`--project-id`, `--org-id`, `--project-name`, `--region-id`, and `--branch` are forwarded to `link`, including the link step inside nested bootstrap when a template is scaffolded. They are not filled from `.neon`; a linked directory is not relinked unless you pass one of those flags.
+`--project-id`, `--org-id`, `--project-name`, `--region-id`, and `--branch` are forwarded to `link`. They select linking. A linked directory is not relinked unless you pass one of those flags.
 
-`--config`, `--no-config`, and `--services` apply on the existing-app and `--skip-template` path. A template's own `neon.ts` is left as the template shipped it. Passing those flags while scaffolding prints a warning and still copies the template as shipped. After a new `neon.ts` on a pinned branch, init runs `env pull`.
-
-`-y` forwards `-y` to `plugins` or `skills`/`mcp`, uses `link -y` (auto-select or print IDs and exit), passes `--default` to nested bootstrap, and forwards `--services none` to `config init`. `--agent` is forwarded to agent setup. `mcp -y` is the global install. Default linking skips the "already linked" confirmation.
+After a new default `neon.ts` on a pinned branch, init runs `env pull` unless link already pulled env or the file declares extra services (those still need `neon config plan` / `neon deploy`).
 
 A failed step stops the rest. `--profile` and `--config-dir` are forwarded to each child. `--output json` and `--output yaml` are refused; the commands init runs print their own output.
 
-`skills` needs Node.js 22.20 or newer. See [`bootstrap`](#scaffold-a-project-bootstrap), [`plugins`](#install-the-neon-plugin-plugins), [`skills`](#install-neon-agent-skills-skills), [`link`](#linking-a-project), and [`mcp`](#install-the-neon-mcp-server-mcp) for what those commands write.
+`skills` needs Node.js 22.20 or newer. See [`plugins`](#install-the-neon-plugin-plugins), [`skills`](#install-neon-agent-skills-skills), [`link`](#linking-a-project), and [`mcp`](#install-the-neon-mcp-server-mcp) for what those commands write.
 
 ## Install the Neon MCP server (`mcp`)
 
 `neon mcp` writes the hosted Neon MCP server (`https://mcp.neon.tech/mcp`) into coding-agent config files.
 
 ```bash
-# Interactive: global or project, then agents, then API key or OAuth, then confirm.
+# Interactive: global or project, then agents, then API key or OAuth.
 $ neon mcp
 
 # Skip prompts. Global config, installed apps else the host CLI agent, reuse or mint an API key.
@@ -843,7 +846,7 @@ $ neon mcp --project-id <project-id>
 $ neon mcp --category querying --category schema
 ```
 
-On a TTY the command asks for config location (global is the default), then agents, then API key vs OAuth, then a summary to confirm before it writes. Detected agents start selected: globally installed agents or project-folder markers such as `.cursor` when the install is project.
+On a TTY the command asks for config location (global is the default), then agents, then API key vs OAuth, then writes. Detected agents start selected: globally installed agents or project-folder markers such as `.cursor` when the install is project.
 
 `-y` skips those questions. `neon mcp -y` writes `https://mcp.neon.tech/mcp` into global config for globally installed apps, else the host CLI agent, reuses an existing Neon MCP API key or mints an account-wide key, leaves write tools enabled, exposes every tool category, and does not pin a project (including from `.neon`). `--agent`, `--project`, `--oauth`, `--read-only`, `--project-id` and `--category` still apply with `-y`. `--read-only` and `--category` are flags only and are never prompted. A linked project-folder install asks whether to pin MCP tools to that `.neon` project (`?projectId=`). If you pin and selected API-key auth, the minted key is limited to that project too. An unlinked project folder does not ask. Global installs never add that param unless you pass `--project-id`. Without a TTY, pass `-y` to mint into every detected agent, `--agent <name>` to name them, or `--oauth` to write the URL only. If `-y` finds no agent, it exits: pass `--agent <name>`, run from a supported agent, or omit `-y` in a terminal to pick. `neon mcp --help` lists the server URL, those `-y` defaults, the supported agent names, and the `--category` values.
 
@@ -856,7 +859,7 @@ The default mints an account-wide API key (or reuses the Bearer already configur
 `neon skills` installs Neon agent skills by running `npx skills add`. It does not call the Neon API. This command needs Node.js 22.20 or newer. The rest of the CLI supports Node.js 20.19 or newer.
 
 ```bash
-# Interactive: this directory, then agents, then skills, then confirm.
+# Interactive: this directory, then agents, then skills.
 $ neon skills
 
 # Skip prompts. This directory, detected agents (project folders, else the host CLI agent), the default skills.
@@ -880,7 +883,7 @@ $ neon skills update -y
 $ neon skills update --global -y
 ```
 
-On a TTY the command asks which agents and which skills, then shows a summary to confirm. Detected agents start selected from project-folder markers such as `.cursor`. Default skills start selected. `neon-postgres-agent-platforms` is offered and starts unselected.
+On a TTY the command asks which agents and which skills, then installs. Detected agents start selected from project-folder markers such as `.cursor`. Default skills start selected. `neon-postgres-agent-platforms` is offered and starts unselected.
 
 `-y` skips those questions and installs the default skills into detected agents: project-folder markers such as `.cursor`, else the agent driving the CLI. `--agent` / `-a` names coding agents and skips the agent picker. `--skill` / `-s` names specific skills and skips the skill picker; it does not select agents. `--global -y` uses installed apps, else the host CLI agent. Without a TTY, pass `-y`, or `--skill <name>` (add `--agent <name>` to name agents). If `-y` finds no agent, it exits: pass `--agent <name>`, run from a supported agent, or omit `-y` in a terminal to pick.
 
@@ -904,7 +907,7 @@ Default table output is the assistant's text. On a TTY that is a spinner, then t
 `neon plugins` installs the Neon agent plugin (`neon-postgres`) by running `npx plugins add`. It does not call the Neon API.
 
 ```bash
-# Interactive: agents, then confirm.
+# Interactive: pick agents, then install.
 $ neon plugins
 
 # Skip prompts. Detected agents (project folders, else the host CLI agent).
@@ -917,7 +920,7 @@ $ neon plugins --agent cursor --agent claude-code
 $ neon plugins --global
 ```
 
-On a TTY the command asks which agents, then shows a summary to confirm. Detected agents start selected from project-folder markers such as `.cursor`. There is one plugin (`neon-postgres`); there is no plugin picker and no `update` subcommand.
+On a TTY the command asks which agents, then installs. Detected agents start selected from project-folder markers such as `.cursor`. There is one plugin (`neon-postgres`); there is no plugin picker and no `update` subcommand.
 
 `-y` skips those questions and installs into detected agents: project-folder markers such as `.cursor`, else the agent driving the CLI. `--agent` / `-a` names coding agents and skips the agent picker. `--global -y` uses installed apps, else the host CLI agent. Without a TTY, pass `-y` or `--agent <name>`. If `-y` finds no agent, it exits: pass `--agent <name>`, run from a supported agent, or omit `-y` in a terminal to pick.
 
@@ -933,12 +936,15 @@ The plugins CLI installs every plugin it finds in the Neon plugin package. Today
 
 `neon snapshots` (alias `neon snapshot`) manages **snapshots** — point-in-time backups of a branch that you can list, rename, expire, restore into a branch, or schedule automatically. Snapshots are a Beta Neon feature and were previously only available in the Console and REST API; this command group brings them to the CLI.
 
-Every sub-command resolves the project through the standard chain (`--project-id`, then the `.neon` context file, then a single-project auto-detect). Branch-scoped sub-commands (`create`, `schedule`) default to the branch pinned in `.neon`, falling back to the project's default branch, and accept `--branch <id|name>`. The `get`, `update`, `delete`, and `restore` sub-commands take a snapshot **id or name** as their positional argument (an id wins; an ambiguous name errors and asks you to use the id).
+Every sub-command resolves the project through the standard chain (`--project-id`, then the `.neon` context file, then a single-project auto-detect). Branch-scoped sub-commands (`create`, `schedule`) default to the branch pinned in `.neon`, falling back to the project's default branch, and accept `--branch <id|name>`. The `get`, `update`, `delete`, and `restore` sub-commands take a snapshot **id, unique name, or slug** as their positional argument. An id wins. A unique name still wins over another snapshot's matching slug, so a name you already use keeps targeting that snapshot. Slug is used when no name matches. An ambiguous name errors and asks you to use the id.
 
 ```bash
 # Snapshot the head of the current/default branch
 neon snapshots create --name pre-migration
 
+# Give the snapshot a slug (unique in the project; omit to let the API generate one)
+neon snapshots create --branch main --name "Before migration" --slug before-migration
+
 # Snapshot a specific branch at a point in time (RFC 3339 timestamp OR LSN — mutually exclusive)
 neon snapshots create --branch main --timestamp 2025-01-01T00:00:00Z
 neon snapshots create --branch main --lsn 0/1F3C8A0 --expires-at 2025-12-31T23:59:59Z
@@ -946,6 +952,7 @@ neon snapshots create --branch main --lsn 0/1F3C8A0 --expires-at 2025-12-31T23:5
 # List / inspect
 neon snapshots list
 neon snapshots get pre-migration
+neon snapshots get before-migration
 
 # Rename or change expiration (omit both to error; --expires-at and --clear-expiration conflict)
 neon snapshots update snap-1234 --name nightly
@@ -1361,7 +1368,7 @@ Id   Name      Project         Created At            Last Used At          Last
 | config                                                                     | `init`, `status`, `plan`, `apply`                                                                            | Drive a branch from `neon.ts`      |
 | deploy                                                                     |                                                                                                              | Alias for `config apply`           |
 | bootstrap                                                                  |                                                                                                              | Scaffold a template, then agent tooling and link |
-| init                                                                       |                                                                                                              | Empty dir: bootstrap. Existing: agents, link, neon.ts |
+| init                                                                       |                                                                                                              | In place: agents, link, neon.ts       |
 | mcp                                                                        |                                                                                                              | Install the Neon MCP server         |
 | plugins                                                                    |                                                                                                              | Install the Neon plugin             |
 | skills                                                                     | `update`                                                                                                     | Install Neon agent skills           |

package/dist/commands/bootstrap.js

@@ -2,12 +2,10 @@ import { t as __exportAll } from "../_chunks/rolldown-runtime-8H4AJuhK.js";
 import { isCi } from "../env.js";
 import { log } from "../log.js";
 import { recordCommandSuccessExtras, recordScaffoldedTemplate } from "../analytics.js";
-import { t as credentialInputs } from "../_chunks/auth_selection-pitMFzDe.js";
 import { getCliName } from "../utils/cli_name.js";
 import { helpCsv, helpEpilogue } from "../utils/help_text.js";
 import { writer } from "../writer.js";
 import { FALLBACK_TEMPLATES, ensureTargetUsable, fetchTemplates, findTemplate, scaffoldTemplate, templateIds } from "../init/bootstrap.js";
-import { spawnCliChild } from "../init/child.js";
 import { agentSetupDoneLabel, formatInitDone, printInitBanner, printInitDone, shouldPrintInitBanner } from "../init/chrome.js";
 import { formatInstallCommand, inferPackageManager, installArgs, installedPackageManagers, resolvePackageManager, runCommand } from "../utils/package_manager.js";
 import { runAuthenticatedLink } from "../init/link.js";
@@ -271,7 +269,9 @@ const runDefaultSteps = async (props, targetDir, pm, neonConfig, template, named
 };
 const executePostScaffold = async (props, targetDir, choices) => {
 	const kids = {
-		...bootstrapChildren(props, targetDir),
+		output: "table",
+		auth: bootstrapAuth(props, targetDir),
+		operations: props.operations,
 		...props.narrate ? { narrate: props.narrate } : {}
 	};
 	let installed = false;
@@ -370,20 +370,22 @@ const hasNeonConfig = (dir) => NEON_CONFIG_FILENAMES.some((name) => existsSync(j
 const logSkippedLink = (pm) => {
 	log.info(`Skipping the Neon link step: \`${getCliName()} link\` reads this project's neon.ts to pull env vars, which needs its dependencies. Run \`${formatInstallCommand(pm)}\`, then \`${getCliName()} link\`.`);
 };
-const bootstrapChildren = (props, targetDir) => {
-	const explicitKey = props.profile ? "" : credentialInputs().apiKeyFlag;
-	return {
-		run: props.run ?? spawnCliChild,
-		forward: {
-			...props.configDir ? { configDir: props.configDir } : {},
-			...props.profile ? { profile: props.profile } : {},
-			apiHost: props.apiHost,
-			contextFile: projectContextFile(targetDir, props.contextFile),
-			...props.analytics === false ? { analytics: false } : {}
-		},
-		...explicitKey ? { authEnv: { NEON_API_KEY: explicitKey } } : {}
-	};
-};
+/**
+* plugins/skills need no Neon auth at all; mcp resolves it itself, in-process, exactly as
+* the standalone `neon mcp` does (see `init/auth.ts`) — this is that shared context.
+*/
+const bootstrapAuth = (props, targetDir) => ({
+	apiClient: props.apiClient,
+	apiKey: props.apiKey,
+	apiHost: props.apiHost,
+	contextFile: projectContextFile(targetDir, props.contextFile),
+	...props.configDir ? { configDir: props.configDir } : {},
+	...props.profile ? { profile: props.profile } : {},
+	...props.oauthHost ? { oauthHost: props.oauthHost } : {},
+	...props.clientId ? { clientId: props.clientId } : {},
+	...props.forceAuth !== void 0 ? { forceAuth: props.forceAuth } : {},
+	...props.allowUnsafeTls !== void 0 ? { allowUnsafeTls: props.allowUnsafeTls } : {}
+});
 /**
 * Initialize a git repository in the scaffolded directory. Just `git init` — we
 * deliberately don't auto-commit, both to avoid failing on a machine with no

package/dist/commands/config.js

@@ -26,6 +26,7 @@ import { packagesToStage, previewGaWarningForConfig, resolveConfig } from "@neon
 import { PushConflictError, apply, assertZipWithinLimits, bundleAsIs, createBranch, describeNativeFinding, enforceLimits, findUndeclaredNativePackages, inspect, isPartialBranchCreateError, loadConfigFromFile as loadConfigFromFile$1, plan, resolveEsbuildEntry, traceNativePackages, zipFunctionBundle } from "@neon/config-runtime";
 //#region src/commands/config.ts
 var config_exports = /* @__PURE__ */ __exportAll({
+	ConfigInstallFailed: () => ConfigInstallFailed,
 	applyCmd: () => applyCmd,
 	applyFlags: () => applyFlags,
 	applyPolicyOnCreate: () => applyPolicyOnCreate,
@@ -38,6 +39,7 @@ var config_exports = /* @__PURE__ */ __exportAll({
 	handler: () => handler,
 	hasNeonConfigFile: () => hasNeonConfigFile,
 	initCmd: () => initCmd,
+	neonConfigFilename: () => neonConfigFilename,
 	planCmd: () => planCmd,
 	status: () => status
 });
@@ -117,8 +119,16 @@ const NEON_CONFIG_FILENAMES = [
 	"neon.js",
 	"neon.mjs"
 ];
+const neonConfigFilename = (dir) => NEON_CONFIG_FILENAMES.find((name) => existsSync(join(dir, name)));
 /** Whether `dir` already has a Neon config file the runtime would load. */
-const hasNeonConfigFile = (dir) => NEON_CONFIG_FILENAMES.some((name) => existsSync(join(dir, name)));
+const hasNeonConfigFile = (dir) => neonConfigFilename(dir) !== void 0;
+var ConfigInstallFailed = class extends Error {
+	constructor(command) {
+		super("Could not install the Neon dependencies.");
+		this.name = "ConfigInstallFailed";
+		this.command = command;
+	}
+};
 const isRecord = (value) => typeof value === "object" && value !== null;
 /**
 * The {@link REQUIRED_PACKAGES} not already declared in the project's package.json
@@ -209,33 +219,44 @@ const seedFromBranch = async (props) => {
 const initCmd = async (props) => {
 	const cwd = props.cwd ?? process.cwd();
 	const run = props.run ?? runCommand;
-	const existing = NEON_CONFIG_FILENAMES.find((name) => existsSync(join(cwd, name)));
-	if (existing) log.info("Found an existing %s — leaving it untouched.", existing);
-	else if (props.fromBranch) {
+	const existing = neonConfigFilename(cwd);
+	if (existing) {
+		if (!props.silent) log.info("Found an existing %s — leaving it untouched.", existing);
+	} else if (props.fromBranch) {
 		const { source, seeded, branchName } = await seedFromBranch(props);
 		writeFileSync(join(cwd, "neon.ts"), source);
-		if (seeded) log.info("Created neon.ts from the live state of %s.", branchName);
-		else log.info("%s declares no services and no branch settings — created neon.ts with the starter policy instead.", branchName);
+		if (!props.silent) {
+			if (seeded) log.info("Created neon.ts from the live state of %s.", branchName);
+			else log.info("%s declares no services and no branch settings — created neon.ts with the starter policy instead.", branchName);
+		}
 	} else {
 		const services = await resolveServices(props);
 		writeFileSync(join(cwd, "neon.ts"), renderNeonConfig(services));
-		if (services.length === 0) log.info("Created neon.ts with a starter policy.");
-		else log.info("Created neon.ts declaring %s.", services.join(", "));
+		if (!props.silent) {
+			if (services.length === 0) log.info("Created neon.ts with a starter policy.");
+			else log.info("Created neon.ts declaring %s.", services.join(", "));
+		}
 		if (services.includes("functions")) scaffoldFunction(cwd);
 	}
 	const missing = missingDependencies(cwd);
-	if (missing.length === 0) log.info("%s are already installed.", REQUIRED_PACKAGES.join(" and "));
-	else {
-		const pm = resolvePackageManager(cwd);
+	if (missing.length === 0) {
+		if (!props.silent) log.info("%s are already installed.", REQUIRED_PACKAGES.join(" and "));
+	} else {
+		const pm = props.packageManager ?? resolvePackageManager(cwd);
 		const args = installArgs(pm, missing);
-		if (props.install === false) log.info("Install the Neon config packages to use neon.ts: %s", formatInstallCommand(pm, missing));
-		else {
+		if (props.install === false) {
+			if (!props.silent) log.info("Install the Neon config packages to use neon.ts: %s", formatInstallCommand(pm, missing));
+		} else {
 			ensureDirectoryGitignored(join(cwd, "node_modules"));
-			log.info("Installing %s with %s…", missing.join(", "), pm);
-			if (!await run(pm, args, cwd)) log.warning("Could not install the config packages automatically. Run by hand: %s", formatInstallCommand(pm, missing));
+			if (!props.silent) log.info("Installing %s with %s…", missing.join(", "), pm);
+			if (!await run(pm, args, cwd)) {
+				const command = formatInstallCommand(pm, missing);
+				if (props.requireInstall) throw new ConfigInstallFailed(command);
+				log.warning("Could not install the config packages automatically. Run by hand: %s", command);
+			}
 		}
 	}
-	log.info("Next: edit neon.ts, then run `neon config plan` to preview and `neon config apply`.");
+	if (!props.silent) log.info("Next: edit neon.ts, then run `neon config plan` to preview and `neon config apply`.");
 };
 const command = "config";
 const describe = "Manage a branch with a neon.ts policy";
@@ -741,4 +762,4 @@ const createBranchFromPolicyOnCheckout = async (props) => {
 	}
 };
 //#endregion
-export { applyCmd, applyFlags, applyPolicyOnCreate, builder, command, createBranchFromPolicyOnCheckout, describe, envFlag, envPullFlag, handler, hasNeonConfigFile, initCmd, planCmd, status, config_exports as t };
+export { ConfigInstallFailed, applyCmd, applyFlags, applyPolicyOnCreate, builder, command, createBranchFromPolicyOnCheckout, describe, envFlag, envPullFlag, handler, hasNeonConfigFile, initCmd, neonConfigFilename, planCmd, status, config_exports as t };

package/dist/commands/dev.js

@@ -13,8 +13,8 @@ import { existsSync, mkdirSync, rmSync, statSync, writeFileSync } from "node:fs"
 import { basename, dirname, join, relative, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import chalk from "chalk";
-import { spawn, spawnSync } from "node:child_process";
 import { bundleAsIs, describeNativeFinding, findUndeclaredNativePackages, resolveEsbuildEntry } from "@neon/config-runtime";
+import { spawn, spawnSync } from "node:child_process";
 import { once } from "node:events";
 import { createServer } from "node:net";
 //#region src/commands/dev.ts

package/dist/commands/index.js

@@ -6,6 +6,9 @@ import { t as env_exports } from "./env.js";
 import { t as config_exports } from "./config.js";
 import { t as projects_exports } from "./projects.js";
 import { t as link_exports } from "./link.js";
+import { t as mcp_exports } from "./mcp.js";
+import { t as plugins_exports } from "./plugins.js";
+import { t as skills_exports } from "./skills.js";
 import { t as bootstrap_exports } from "./bootstrap.js";
 import { t as branches_exports } from "./branches.js";
 import { t as bucket_exports } from "./bucket.js";
@@ -23,17 +26,14 @@ import { t as init_exports } from "./init.js";
 import { t as inspect_exports } from "./inspect.js";
 import { t as ip_allow_exports } from "./ip_allow.js";
 import { t as logs_exports } from "./logs.js";
-import { t as mcp_exports } from "./mcp.js";
 import { t as neon_auth_exports } from "./neon_auth.js";
 import { t as open_exports } from "./open.js";
 import { t as operations_exports } from "./operations.js";
 import { t as orgs_exports } from "./orgs.js";
-import { t as plugins_exports } from "./plugins.js";
 import { t as profile_exports } from "./profile.js";
 import { t as psql_exports } from "./psql.js";
 import { t as roles_exports } from "./roles.js";
 import { t as set_context_exports } from "./set_context.js";
-import { t as skills_exports } from "./skills.js";
 import { t as snapshots_exports } from "./snapshots.js";
 import { t as status_exports } from "./status.js";
 import { t as triggers_exports } from "./triggers.js";