@rebasepro/cli 0.16.0 → 0.16.1-canary.g1ad04b7

package/dist/bundle.d.ts

@@ -193,6 +193,25 @@ export interface VendorResult {
  * the upload is compressed: crossing it means "getting close", not "will fail".
  */
 export declare const VENDOR_SIZE_WARN_BYTES: number;
+/**
+ * Where vendoring stops being an optimisation and becomes a bundle nobody can
+ * deploy.
+ *
+ * Past this, shipping the tree anyway trades a faster cold start for a 413 — and
+ * the 413 arrives at deploy time, after a build nobody watches, with a remedy
+ * (`--no-vendor`) that requires knowing this happened. Unvendoring here costs
+ * 40–60s of cold start and produces a bundle that uploads; that is the better
+ * side of the trade to be on by default.
+ *
+ * 200 MB assumes a **2x** floor on compression, which is pessimistic for a tree
+ * of JavaScript (3–5x is typical) and deliberately so: source maps and prebuilt
+ * binaries compress far worse than source, and the failure this prevents is
+ * asymmetric — a bundle refused at the door versus a minute of cold start.
+ * `--vendor` overrides it, for a deploy path with no upload at all (a Dockerfile
+ * built from source, where the tree is copied into an image and the control
+ * plane never sees it).
+ */
+export declare const VENDOR_SIZE_MAX_BYTES: number;
 /**
  * Install the bundle's declared dependencies into the bundle itself.
  *

package/dist/commands/cloud/deployments.d.ts

@@ -37,6 +37,47 @@ export declare function triggerInfo(dep: DeploymentRow): {
 };
 /** Shape one deployment row into the stable JSON view the CLI publishes. */
 export declare function deploymentView(dep: DeploymentRow): Record<string, unknown>;
+/** What `POST /api/functions/deploy/cancel` answers. */
+export interface CancelResponse {
+    success: boolean;
+    /**
+     * The deployment that was cancelled — `null` when there was none.
+     *
+     * Nullable because "nothing was in flight" is a real, successful outcome
+     * and not an error: a project's `status` column can claim `deploying` while
+     * no deployment row backs the claim, and cancelling is what clears it.
+     */
+    deploymentId: string | null;
+    buildJobDeleted: boolean;
+    /** The request cleared a stuck `deploying` claim rather than stopping a build. */
+    unstranded?: boolean;
+    /** The status the project settled on when it did. */
+    projectStatus?: string | null;
+}
+/**
+ * What `rebase cloud cancel` says it did.
+ *
+ * Split out of the command because there are now two outcomes behind one
+ * `success: true`, and only one of them is "a build was stopped". The control
+ * plane learned to clear a project stranded at `deploying` with no deployment
+ * row behind it — the state `prospector` was wedged in for five days — and it
+ * reports that through this same endpoint. An unbranched caller printed
+ * "Cancelled deployment null" for it, which reads as a bug in the thing that
+ * had just fixed the bug.
+ *
+ * The ABSENT ID is what decides, not the `unstranded` flag: the flag is the
+ * server being explicit, and it is the newer half of the contract. Branching on
+ * the id means a client that meets a control plane which grew the behaviour
+ * without the flag still says something true.
+ */
+export declare function cancelView(res: CancelResponse): {
+    /** The headline, for `success()`. */
+    headline: string;
+    /** Dimmed follow-ups, printed under it. */
+    notes: string[];
+    /** The stable JSON view, which is what a piped run gets. */
+    json: Record<string, unknown>;
+};
 /**
  * Rows shown when `--limit` is not given.
  *

package/dist/commands/cloud/projects.d.ts

@@ -1,4 +1,4 @@
-import { type DeployTarget, type CloudClient } from "./context";
+import { type DeployTarget, type CloudClient } from "./context.js";
 export declare function listProjects(rawArgs: string[]): Promise<void>;
 /**
  * Where this project says it runs.
@@ -9,8 +9,9 @@ export declare function listProjects(rawArgs: string[]): Promise<void>;
  * never contradicted by a failure; it just sits in the record. The CLI used to
  * default to `hetzner`/`nbg1` unconditionally, which is how projects running on
  * our GKE cluster came to describe themselves as Hetzner in the console — and
- * `provider` is half the Stripe compute lookup key (`compute_<provider>_<vmSize>`),
- * so that is a mispricing, not a cosmetic slip.
+ * `provider` also decides which substrate's rules a project's dials are clamped
+ * to — Autopilot's 250m floor and 1:1-6.5:1 band do not apply on Hetzner or EKS
+ * — so a wrong value here resizes pods, it is not a cosmetic slip.
  *
  * The control plane already publishes the infrastructure that actually exists,
  * and the console's create wizard reads it. Ask the same question here.
@@ -39,10 +40,19 @@ export declare const CREATE_PROJECT_FLAGS: {
     readonly "--branch": StringConstructor;
     readonly "--provider": StringConstructor;
     readonly "--region": StringConstructor;
-    readonly "--vm-size": StringConstructor;
     readonly "--org": StringConstructor;
     readonly "--link": BooleanConstructor;
     readonly "-n": "--name";
+    readonly "--cpu": StringConstructor;
+    readonly "--memory": StringConstructor;
+    readonly "--replicas": StringConstructor;
+    readonly "--spot": StringConstructor;
+    readonly "--scale-to-zero": StringConstructor;
+    readonly "--db-mode": StringConstructor;
+    readonly "--db-instances": StringConstructor;
+    readonly "--db-cpu": StringConstructor;
+    readonly "--db-memory": StringConstructor;
+    readonly "--storage": StringConstructor;
 };
 export declare function createProject(rawArgs: string[]): Promise<void>;
 /**

package/dist/commands/cloud/resources.d.ts

@@ -106,7 +106,16 @@ export declare function resourcesCommand(action: string | undefined, rawArgs: st
  * the same shape `buildSettingsPatch` uses. Returns an error string rather than
  * throwing, because the caller owns how a refusal is printed in JSON mode.
  */
-export declare function buildDialPatch(rawArgs: string[]): {
+export declare function buildDialPatch(rawArgs: string[], 
+/**
+ * `requireOne: false` for `projects create`, where naming no dial is the
+ * ordinary case — a new project takes the platform default. On
+ * `resources set` a patch with nothing in it is a typo, and saying so beats
+ * a success message for a change nobody made.
+ */
+opts?: {
+    requireOne?: boolean;
+}): {
     patch: Record<string, unknown>;
     error?: string;
 };

package/dist/commands/doctor.d.ts

@@ -1,4 +1,4 @@
-import { type LibpqUrlFinding } from "../utils/libpq-url";
+import { type LibpqUrlFinding } from "../utils/libpq-url.js";
 /**
  * Find connection strings libpq cannot parse, anywhere in the project.
  *

package/dist/commands/init.d.ts

@@ -1,4 +1,4 @@
-import type { PackageManager, PMCommands } from "../utils/package-manager";
+import type { PackageManager, PMCommands } from "../utils/package-manager.js";
 /**
  * Every scaffolded file that carries a `{{PLACEHOLDER}}`.
  *

package/dist/function-portability.d.ts

@@ -0,0 +1,45 @@
+/** What a single finding is about. */
+export type PortabilityIssueKind = "node-builtin" | "node-only-package" | "module-scope-env" | "root-barrel-import" | "unknown-package";
+export interface PortabilityIssue {
+    kind: PortabilityIssueKind;
+    /** 1-based line in the function file. */
+    line: number;
+    /** One sentence, already phrased for a terminal. */
+    message: string;
+    /**
+     * Whether this is a problem *today*, on Node, rather than only a constraint
+     * on where the function could run. Exactly one kind is:
+     * `module-scope-env`, which is a latent crash on any host where a variable
+     * happens to be unset at import time, and takes every other function in the
+     * same directory down with it — the loader reports a file that throws on
+     * import as simply "skipped".
+     */
+    actionable: boolean;
+}
+export interface FunctionPortability {
+    /** Function name — the filename without extension, as it mounts. */
+    name: string;
+    /** Path relative to the project root. */
+    file: string;
+    /** Empty when the function depends on nothing host-specific. */
+    issues: PortabilityIssue[];
+    /** True when `issues` contains nothing that pins it to Node. */
+    portable: boolean;
+}
+/** Analyse one function file's source. Exported for testing. */
+export declare function analyseFunctionSource(source: string, name: string, file: string): FunctionPortability;
+/**
+ * Analyse every function in a directory.
+ *
+ * @param functionsDir Absolute path to the functions directory.
+ * @param projectRoot  For rendering paths people recognise.
+ */
+export declare function analyseFunctionsDirectory(functionsDir: string, projectRoot: string): FunctionPortability[];
+/**
+ * The lines to print after a build, or nothing at all.
+ *
+ * Silent when every function is portable and nothing is actionable, because a
+ * report that always prints is a report nobody reads. Actionable findings are
+ * always shown; the rest collapse to a single count with a pointer.
+ */
+export declare function summarisePortability(results: FunctionPortability[]): string[];

package/dist/index.d.ts

@@ -1,17 +1,17 @@
-export * from "./cli";
-export * from "./commands/init";
-export * from "./commands/schema";
-export * from "./commands/db";
-export * from "./commands/dev";
-export * from "./commands/build";
-export * from "./commands/eject";
-export * from "./commands/start";
-export * from "./commands/auth";
-export * from "./commands/doctor";
-export * from "./commands/generate_sdk";
-export * from "./commands/cloud";
-export * from "./commands/apps";
-export * from "./utils/project";
-export * from "./utils/package-manager";
-export * from "./manifest";
-export * from "./bundle";
+export * from "./cli.js";
+export * from "./commands/init.js";
+export * from "./commands/schema.js";
+export * from "./commands/db.js";
+export * from "./commands/dev.js";
+export * from "./commands/build.js";
+export * from "./commands/eject.js";
+export * from "./commands/start.js";
+export * from "./commands/auth.js";
+export * from "./commands/doctor.js";
+export * from "./commands/generate_sdk.js";
+export * from "./commands/cloud/index.js";
+export * from "./commands/apps.js";
+export * from "./utils/project.js";
+export * from "./utils/package-manager.js";
+export * from "./manifest.js";
+export * from "./bundle.js";