neon-init 0.13.1 → 0.15.0

package/dist/lib/phases/setup.d.ts

@@ -0,0 +1,41 @@
+import { PhaseResponse } from "../types.js";
+import { NeonFeature } from "../bootstrap.js";
+
+//#region src/lib/phases/setup.d.ts
+interface SetupPhaseOptions {
+  agent?: string;
+  /** The IDE/editor the user is running in (e.g. "cursor", "vscode") — reported by agent */
+  ide?: string;
+  /** Whether the directory already contains an application */
+  hasApp?: boolean;
+  /** Template ID to scaffold (when bootstrapping a new project) */
+  template?: string;
+  /** Neon features required by the selected template */
+  templateRequires?: NeonFeature[];
+  /** Neon features selected by the user (brownfield flows) */
+  features?: NeonFeature[];
+  mcpConfigured?: boolean | null;
+  connectionString?: boolean | null;
+  connectionParams?: string;
+  framework?: string;
+  orm?: string;
+  migrationTool?: string;
+  migrationDir?: string;
+  isVscodeIde?: boolean | null;
+  mode?: "defaults" | "customize";
+  mcpScope?: "global" | "project" | "none";
+  skillsScope?: "global" | "project";
+  installExtension?: boolean;
+  execute?: boolean;
+}
+/**
+ * Comprehensive setup phase: inspects repo state, collects user preferences,
+ * then batches all installation commands together.
+ *
+ * With --data JSON, the agent sends inspection results AND user preferences
+ * in a single call, so the CLI can go straight to installation.
+ */
+declare function handleSetupPhase(options: SetupPhaseOptions): Promise<PhaseResponse>;
+//#endregion
+export { SetupPhaseOptions, handleSetupPhase };
+//# sourceMappingURL=setup.d.ts.map

package/dist/lib/phases/setup.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"setup.d.ts","names":[],"sources":["../../../src/lib/phases/setup.ts"],"mappings":";;;;UAsBiB,iBAAA;;EAAA;EAAiB,GAAA,CAAA,EAAA,MAAA;;QAWtB,CAAA,EAAA,OAAA;EAAW;EA0BD,QAAA,CAAA,EAAA,MAAA;EAAgB;kBAC5B,CAAA,EA7BU,WA6BV,EAAA;;UACP,CAAA,EA5BS,WA4BT,EAAA;EAAO,aAAA,CAAA,EAAA,OAAA,GAAA,IAAA;;;;;;;;;;;;;;;;;;;;;iBAFY,gBAAA,UACZ,oBACP,QAAQ"}