@neondatabase/config-runtime 0.0.0 → 0.2.0

package/src/v1.ts

@@ -1,74 +0,0 @@
-/**
- * `@neondatabase/config-runtime/v1` — the imperative runtime for Config-as-Code on the
- * Neon Platform.
- *
- * `@neondatabase/config` is the **authoring** surface: `defineConfig`, types, and schemas
- * you import from `neon.ts`. It is intentionally free of heavy/native dependencies.
- *
- * This package is the **runtime**: it reads a branch's live state, diffs a policy against
- * it, applies changes, and bundles + deploys Neon Functions. Bundling pulls in `esbuild`
- * (a native binary), so deploy-side consumers (the neonctl CLI, CI scripts) import *this*
- * package — and a `neon.ts` that only imports `defineConfig` never drags esbuild into the
- * user's dependency tree.
- *
- * ```ts
- * import config from "../neon";
- * import { inspect, plan, apply } from "@neondatabase/config-runtime/v1";
- *
- * const target = { projectId: "patient-art-12345", branchId: "main" };
- * const diff = await plan(config, target);     // dry-run plan, no mutations
- * await apply(config, target);                 // apply the policy to a branch
- * const live = await inspect(target);          // read the branch's live state
- * ```
- *
- * `plan` / `apply` mirror the Terraform mental model. No CLI commands are shipped here, and
- * no `.neon` files or `NEON_*` env vars are read — resolve project/branch in your CLI (e.g.
- * neonctl) and pass them in.
- */
-
-export type {
-	AppliedChange,
-	Config,
-	ConflictReport,
-	LoadConfigOptions,
-	NeonApi,
-	PushResult,
-} from "@neondatabase/config";
-// ─── Re-exports from @neondatabase/config for convenience ─────────────────────
-// Runtime callers usually want a few authoring-side symbols alongside the operations
-// (the errors `apply`/`pushConfig` throw, the result types they return, and the loader).
-// Re-export the common ones so a deploy script can import everything it needs from one
-// place, while `neon.ts` keeps importing the lean `@neondatabase/config`.
-export {
-	ConfigLoadError,
-	ConfigValidationError,
-	createNeonApiFromOptions,
-	createRealNeonApi,
-	defineConfig,
-	ErrorCode,
-	loadConfigFromFile,
-	MissingContextError,
-	PlatformError,
-	PushAbortedError,
-	PushConflictError,
-} from "@neondatabase/config";
-// ─── Function bundling (esbuild + zip) ────────────────────────────────────────
-export { buildFunctionBundle } from "./lib/function-bundle.js";
-// ─── Operations (intent-revealing entry points) ───────────────────────────────
-export type {
-	ApplyOptions,
-	ConfigOperationOptions,
-} from "./lib/operations.js";
-export { apply, inspect, plan } from "./lib/operations.js";
-// ─── Engine (advanced / programmatic use) ─────────────────────────────────────
-export type {
-	PullConfigOptions,
-	PulledBranchConfig,
-	PulledPreview,
-} from "./lib/pull-config.js";
-export { pullConfig } from "./lib/pull-config.js";
-export type {
-	PushConfigOptions,
-	PushConfirmContext,
-} from "./lib/push-config.js";
-export { pushConfig } from "./lib/push-config.js";

package/tsconfig.json

@@ -1,4 +0,0 @@
-{
-	"extends": "../../tsconfig.base.json",
-	"include": ["src", "e2e", "vitest.config.ts", "vitest.e2e.config.ts", "tsdown.config.ts"]
-}

package/tsdown.config.ts

@@ -1,22 +0,0 @@
-import { defineConfig } from "tsdown";
-
-export default defineConfig({
-	name: "@neondatabase/config-runtime",
-	bundle: false,
-	clean: true,
-	dts: true,
-	entry: [
-		"src/index.ts",
-		"src/v1.ts",
-		"src/lib/**/*.ts",
-		"!src/**/*.test.*",
-		"!src/lib/fake-neon-api.ts",
-	],
-	format: "esm",
-	outDir: "dist",
-	treeshake: true,
-	// esbuild and fflate are real, auto-installed dependencies of this package — but they
-	// must stay external so the published runtime resolves them from node_modules rather
-	// than inlining esbuild's native binary into the bundle.
-	external: ["esbuild", "fflate", "@neondatabase/config"],
-});

package/vitest.config.ts

@@ -1,19 +0,0 @@
-import { defineConfig } from "vitest/config";
-
-export default defineConfig({
-	test: {
-		clearMocks: true,
-		mockReset: true,
-		unstubEnvs: true,
-		coverage: {
-			all: true,
-			include: ["src"],
-			exclude: ["src/**/*.test.ts"],
-			reporter: ["html", "lcov"],
-		},
-		// Skip e2e tests (which talk to the real Neon API) in the standard suite — they
-		// run via `pnpm test:e2e` against `vitest.e2e.config.ts`.
-		exclude: ["lib", "node_modules", "dist", "**/*.e2e.test.ts", "e2e/**"],
-		setupFiles: ["console-fail-test/setup"],
-	},
-});

package/vitest.e2e.config.ts

@@ -1,29 +0,0 @@
-import { defineConfig } from "vitest/config";
-
-/**
- * Vitest config for end-to-end tests that hit the **real** Neon API.
- *
- * - Matches `**\/*.e2e.test.ts` only — the standard `test:ci` config explicitly excludes
- *   this pattern so the two suites never collide.
- * - Uses long per-test timeouts because real project creation / deletion can take 10+s.
- * - Forces single-threaded execution to avoid quota / rate-limit interference between
- *   tests (`pool: "forks"` with `singleFork: true`).
- * - Loads `.env` via Vitest's built-in dotenv support so `NEON_API_KEY` (and optionally
- *   `NEON_ORG_ID`) become `process.env` entries inside the tests.
- */
-export default defineConfig({
-	test: {
-		include: ["src/**/*.e2e.test.ts", "e2e/**/*.test.ts"],
-		exclude: ["node_modules", "dist"],
-		setupFiles: ["./e2e/load-env.ts", "./e2e/setup.ts"],
-		testTimeout: 120_000,
-		hookTimeout: 120_000,
-		pool: "forks",
-		poolOptions: {
-			forks: {
-				singleFork: true,
-			},
-		},
-		reporters: ["verbose"],
-	},
-});