@rebasepro/types 0.11.0 → 0.11.1-canary.g8caabf3

package/dist/types/data_source.d.ts

@@ -3,7 +3,7 @@ import { WhereFilterOp } from "./filter-operators";
  * Describes the capabilities and features supported by a data source (driver).
  *
  * Each driver (Postgres, Firebase, MongoDB, etc.) declares which features it
- * supports. The CMS uses this descriptor to:
+ * supports. The admin uses this descriptor to:
  * - Show/hide editor tabs (e.g. Relations for SQL, Subcollections for Firebase)
  * - Filter the property type picker (e.g. `relation` for SQL, `reference` for Firebase)
  * - Toggle driver-specific form controls (e.g. `columnType` for SQL)

package/dist/types/database_adapter.d.ts

@@ -93,17 +93,22 @@ export interface DatabaseAdapterInitConfig {
     /** The shared collection registry to register into. */
     collectionRegistry: CollectionRegistryInterface;
     /**
-     * How the server is being run — see `RebaseBackendConfig.mode`.
+     * Whether this driver should describe its own schema.
      *
-     * In `"baas"` mode `collections` is empty by design: a driver that can
-     * describe its own schema should introspect the database and report the
-     * collections it found back on `InitializedDriver.collections`. Drivers
-     * that cannot introspect may ignore this.
+     * True when the project declared no collections, so there is nothing to
+     * serve unless the driver reads the live database and reports what it found
+     * on `InitializedDriver.collections`. Drivers that cannot introspect may
+     * ignore it — `initializeRebaseBackend` fails the boot with their name
+     * rather than serving nothing.
+     *
+     * This was a `mode: "cms" | "baas"` flag, which was never independent of
+     * `collections`: every consumer already required the list to be empty
+     * before acting on it, so the flag could only ever agree or contradict.
      */
-    mode?: "cms" | "baas";
+    introspectCollections?: boolean;
     /**
-     * `baas`-mode options — see `RebaseBackendConfig.baas`. Drivers that
-     * introspect should honour `unprotectedTables`.
+     * Options for an introspecting driver — see `RebaseBackendConfig.baas`.
+     * Drivers that introspect should honour `unprotectedTables`.
      */
     baas?: {
         unprotectedTables?: "exclude" | "serve";

package/dist/types/entity_callbacks.d.ts

@@ -69,7 +69,7 @@ export interface AfterReadProps<M extends Record<string, unknown> = Record<strin
      */
     collection: CollectionConfig<M>;
     /**
-     * Full path of the CMS where this collection is being fetched.
+     * Full path of the admin where this collection is being fetched.
      * Might contain unresolved aliases.
      */
     path: string;
@@ -106,7 +106,7 @@ export interface AfterSaveProps<M extends Record<string, unknown> = Record<strin
      */
     collection: CollectionConfig<M>;
     /**
-     * Full path of the CMS where this entity is being saved.
+     * Full path of the admin where this entity is being saved.
      * Might contain unresolved aliases.
      */
     path: string;

package/dist/types/project_manifest.d.ts

@@ -29,24 +29,42 @@
  *
  * - `backend` — the collections/hooks/functions that define the project's API.
  *   Exactly one per *project* (not per repository); the registry enforces it.
- * - `static`  — a pre-built client bundle (SPA, static site) served over CDN.
- * - `admin`   — the Rebase admin panel, either hosted by the platform or built
- *   into this repository.
- * - `mobile`  — a native app. Registration only: it gets client credentials and
- *   configuration, and is never built or hosted here.
- * - `custom`  — an arbitrary container image built from a Dockerfile. The eject
- *   hatch: full control, no managed-runtime guarantees.
+ * - `static`  — a pre-built client bundle (SPA, static site), served from the
+ *   backend process at its declared `path` or from a CDN. The admin panel is
+ *   one of these: it is an app in the user's repository like any other.
+ *
+ * That is the whole list. Ownership of the server process is a property of the
+ * backend app ({@link RebaseBackendAppConfig.runtime}), not an app type.
  */
-export type RebaseAppType = "backend" | "static" | "admin" | "mobile" | "custom";
+export type RebaseAppType = "backend" | "static";
 /**
  * The backend app: the project's API surface.
  *
  * Paths are relative to the directory holding `rebase.json`. The defaults match
  * the layout `rebase init` scaffolds, so a stock project may declare simply
- * `{ "type": "backend" }`.
+ * `{ "type": "backend", "runtime": "managed" }`.
  */
 export interface RebaseBackendAppConfig {
     type: "backend";
+    /**
+     * Who owns the process this backend runs in.
+     *
+     * - `managed` — the platform's runtime image boots this project's bundle.
+     *   You supply collections, functions, crons and schema; Rebase supplies the
+     *   server.
+     * - `custom` — this repository builds its own image and entrypoint. The
+     *   escape hatch: full control, no managed-runtime guarantees.
+     *
+     * Independent of *where* it runs. Both run on Rebase Cloud and both
+     * self-host — the destination lives in `.rebase/cloud.json`, not here. See
+     * `docker/docker-compose.selfhost.yml`, which boots a managed bundle on a
+     * developer's own Docker host.
+     *
+     * This is authored rather than inferred on purpose. It is the single most
+     * consequential fact about a deployment, and inferring it is what used to
+     * land projects on the custom runtime without anyone choosing it.
+     */
+    runtime: "managed" | "custom";
     /** Directory of the config package (collections + index). Default `config`. */
     config?: string;
     /** Directory of server functions. Default `backend/functions`. */
@@ -58,22 +76,23 @@ export interface RebaseBackendAppConfig {
      * Default `backend/src/schema.generated.ts`.
      */
     schema?: string;
-    /**
-     * Which collections source the runtime uses.
-     *
-     * - `cms` (default) — collections come from the config package.
-     * - `baas` — collections are introspected from the live database at boot and
-     *   the config package is not required.
-     */
-    mode?: "cms" | "baas";
     /**
      * Module path (relative to `config`) exporting the auth users collection as
      * its default export. Default `collections/users`.
      */
     usersCollection?: string;
+    /**
+     * `runtime: "custom"` only. Dockerfile path relative to the repository root.
+     * Default `Dockerfile`.
+     */
+    dockerfile?: string;
+    /** `runtime: "custom"` only. Build context relative to the root. Default `.`. */
+    context?: string;
+    /** `runtime: "custom"` only. Port the container listens on. Default 8080. */
+    port?: number;
 }
 /**
- * A static client bundle — SPA or static site — built here and served from CDN.
+ * A static client bundle — SPA or static site — built here and served at `path`.
  */
 export interface RebaseStaticAppConfig {
     type: "static";
@@ -84,54 +103,27 @@ export interface RebaseStaticAppConfig {
     /** Directory of built assets, relative to the repository root. */
     output: string;
     /**
-     * Serve `index.html` for unmatched paths (client-side routing).
+     * Public base path this app is served under. Default `/`.
+     *
+     * Several static apps run in one process, each at its own path — the API at
+     * `/api`, a site at `/`, the admin at `/admin` — which is what keeps a
+     * self-hosted deployment a single container.
+     *
+     * **This is a build-time input, not only a serving concern.** An app mounted
+     * at `/admin` must be *built* for `/admin` (Vite's `base`), or `index.html`
+     * loads and every asset 404s: a blank page with no server error. `rebase
+     * build` passes it as `REBASE_APP_BASE` and asserts the emitted HTML honours
+     * it. Changing this value requires rebuilding the app.
+     */
+    path?: string;
+    /**
+     * Serve `index.html` for unmatched paths under `path` (client-side routing).
      * Default `true` — the overwhelmingly common case for a client app, and a
      * static *site* generator emits real files for its routes anyway.
      */
     spa?: boolean;
 }
-/**
- * The admin panel.
- *
- * `hosted` is the default and means the platform serves it — nothing is built
- * into this repository and nothing ships in the bundle. `bundled` builds it here,
- * which is what a self-hosted or air-gapped deployment wants.
- */
-export interface RebaseAdminAppConfig {
-    type: "admin";
-    mode?: "hosted" | "bundled";
-    /** Only for `bundled`: package directory containing the admin sources. */
-    root?: string;
-    /** Only for `bundled`: build command. */
-    build?: string;
-    /** Only for `bundled`: directory of built assets. */
-    output?: string;
-}
-/**
- * A native app. Registered for credentials and configuration; never built here.
- */
-export interface RebaseMobileAppConfig {
-    type: "mobile";
-    platform: "ios" | "android" | "other";
-}
-/**
- * An app built from a Dockerfile into an arbitrary image.
- *
- * This is the deliberate escape hatch. A project containing one is not eligible
- * for the managed runtime — the platform cannot make guarantees about an image
- * it did not build — but it still deploys, and nothing else about the project
- * changes.
- */
-export interface RebaseCustomAppConfig {
-    type: "custom";
-    /** Dockerfile path relative to the repository root. */
-    dockerfile?: string;
-    /** Build context relative to the repository root. Default `.`. */
-    context?: string;
-    /** Port the container listens on. Default 8080. */
-    port?: number;
-}
-export type RebaseAppConfig = RebaseBackendAppConfig | RebaseStaticAppConfig | RebaseAdminAppConfig | RebaseMobileAppConfig | RebaseCustomAppConfig;
+export type RebaseAppConfig = RebaseBackendAppConfig | RebaseStaticAppConfig;
 /**
  * `rebase.json` — the authored project manifest.
  */
@@ -139,13 +131,17 @@ export interface RebaseProjectManifest {
     /** JSON Schema URL, for editor completion. Ignored by the tooling. */
     $schema?: string;
     /**
-     * The runtime **major** this project targets, as a semver range
+     * The runtime contract **major** this project targets, as a semver range
      * (e.g. `^1`, `~1.4`, or an exact `1.4.2` to pin).
      *
      * The platform upgrades patches and minors underneath a project without
      * asking; it never crosses a major. See {@link RUNTIME_CONTRACT_VERSION}.
+     *
+     * Named `rebase` rather than `runtime` so that `runtime` means exactly one
+     * thing — {@link RebaseBackendAppConfig.runtime}, who owns the process. It
+     * reads like `engines` in a `package.json`, which is what it is.
      */
-    runtime: string;
+    rebase: string;
     /**
      * Apps this repository contributes, keyed by app name. The key is the app's
      * identity within the project: it is what `rebase deploy <app>` names, what
@@ -192,8 +188,16 @@ export interface ManagedCompatibility {
  * not read. A runtime accepts any bundle whose `bundleFormat` is less than or
  * equal to its own — old bundles keep booting on new runtimes, which is the
  * whole point of separating the artifact from the engine.
+ *
+ * - **1** — `mode: "cms" | "baas" | "static"`, `entry.static` a single directory
+ *   string, `entry.admin` for a bundled admin panel.
+ * - **2** — `kind: "backend" | "static"`, `entry.static` a list of
+ *   {@link RebaseBundleStatic}, `entry.admin` removed. A format-1 runtime reading
+ *   one of these would find no `mode` and an array where it expects a string, so
+ *   the bump is what turns that into a refusal to boot instead of a bundle that
+ *   starts and serves nothing.
  */
-export declare const BUNDLE_FORMAT_VERSION = 1;
+export declare const BUNDLE_FORMAT_VERSION = 2;
 /**
  * The runtime contract major.
  *
@@ -217,10 +221,24 @@ export interface RebaseBundleEntrypoints {
     schema?: string;
     /** Module exporting the auth users collection (default export). */
     usersCollection?: string;
-    /** Built admin assets, when the admin panel is bundled rather than hosted. */
-    admin?: string;
-    /** Built static assets to serve from the runtime, when not on a CDN. */
-    static?: string;
+    /**
+     * Built static apps to serve from this process, in declaration order.
+     *
+     * A list rather than a single directory because one process serves several
+     * apps at different paths — a site at `/` and the admin at `/admin`. The
+     * runtime mounts them longest-path-first so the `/`-rooted app's catch-all
+     * does not claim its siblings' URLs.
+     */
+    static?: RebaseBundleStatic[];
+}
+/** One built static app inside a bundle. */
+export interface RebaseBundleStatic {
+    /** Public base path, e.g. `/` or `/admin`. */
+    path: string;
+    /** Bundle-relative directory holding the built assets. */
+    dir: string;
+    /** Serve `index.html` for unmatched paths under `path`. */
+    spa: boolean;
 }
 /**
  * A native module found in the dependency closure.
@@ -263,15 +281,17 @@ export interface RebaseBundleManifest {
     /**
      * What the runtime does with this bundle.
      *
-     * - `cms` — a backend with declared collections; the runtime provisions their
-     *   tables and serves the data API.
-     * - `baas` — a backend that introspects an existing database rather than
-     *   declaring collections.
-     * - `static` — no backend at all: the bundle is a built SPA (`entry.static`),
-     *   and the runtime only serves those assets. No database, no data sources —
-     *   this is how a `static`/`admin` app runs on the same image as the backend.
+     * - `backend` — boot the full server: database, auth and the data API, plus
+     *   any static apps in `entry.static`.
+     * - `static` — no backend at all: serve `entry.static` and nothing else. No
+     *   database, no auth, no data sources. This is how a static app runs on the
+     *   same image as the backend.
+     *
+     * Replaces an earlier `mode: "cms" | "baas" | "static"`. The cms/baas
+     * distinction was never a third kind of thing — it is simply whether
+     * `entry.config` is present, so it is derived rather than declared.
      */
-    mode: "cms" | "baas" | "static";
+    kind: "backend" | "static";
     entry: RebaseBundleEntrypoints;
     /** Collection slugs contained in the bundle, for quick inspection. */
     collections?: string[];
@@ -325,7 +345,6 @@ export interface RebaseProjectContract {
         version: string;
         contract: number;
     };
-    mode: "cms" | "baas";
     /** Full collection definitions, serialized — the input to SDK generation. */
     collections: unknown[];
     /** Collection slugs, for cheap inspection without parsing the definitions. */

package/dist/types/properties.d.ts

@@ -113,7 +113,7 @@ export interface BaseProperty<CustomProps = unknown> {
     description?: string;
     /**
      * You can use this prop to reuse a property that has been defined
-     * in the top level of the CMS in the prop `fields`.
+     * in the top level of the admin in the prop `fields`.
      * All the configuration will be taken from the inherited config, and
      * overwritten by the current property config.
      */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@rebasepro/types",
   "type": "module",
-  "version": "0.11.0",
+  "version": "0.11.1-canary.g8caabf3",
   "description": "Rebase type definitions — shared interfaces and controller types",
   "funding": {
     "url": "https://github.com/sponsors/rebaseco"

package/src/controllers/collection_registry.ts

@@ -11,7 +11,7 @@ export type CollectionRegistryController<
 > = {
 
     /**
-     * List of the mapped collections in the CMS.
+     * List of the mapped collections in the admin.
      * Each entry relates to a collection in the root database.
      * Each of the navigation entries in this field
      * generates an entry in the main menu.

package/src/controllers/data.ts

@@ -116,12 +116,12 @@ export interface FindResponse<M extends Record<string, unknown> = Record<string,
 
 
 /**
- * Fluent query builder for the **admin CMS** — resolves to `FindResponse<M>`
+ * Fluent query builder for the **admin admin** — resolves to `FindResponse<M>`
  * (Snapshot-wrapped rows).
  *
  * @internal App developers should use {@link SDKQueryBuilderInterface}
  * (flat rows, returned by `client.data.*` / `context.data.*`). This
- * Snapshot-flavored variant backs the admin CMS internals only.
+ * Snapshot-flavored variant backs the admin admin internals only.
  *
  * @group Data
  */
@@ -138,13 +138,13 @@ export interface QueryBuilderInterface<M extends Record<string, unknown> = Recor
 }
 
 /**
- * A single collection's CRUD accessor for the **admin CMS** — every method
+ * A single collection's CRUD accessor for the **admin admin** — every method
  * resolves to `Snapshot`-wrapped rows (`FindResponse<M>` / `Snapshot<M>`).
  *
  * @internal App developers do **not** use this. The public, symmetric surface
  * is {@link SDKCollectionClient} (flat rows), exposed as `client.data.products`
  * in the SDK and `context.data.products` in framework callbacks. This
- * Snapshot-flavored accessor backs the admin CMS view-model only.
+ * Snapshot-flavored accessor backs the admin admin view-model only.
  *
  * @group Data
  */
@@ -269,7 +269,7 @@ export interface SDKQueryBuilderInterface<M extends Record<string, unknown> = Re
  * SDK collection client — returns flat rows, no Entity wrapper.
  *
  * This is the public API surface for app developers using
- * `createRebaseClient()`. CMS internals use `CollectionAccessor` instead.
+ * `createRebaseClient()`. admin internals use `CollectionAccessor` instead.
  *
  * Type parameters:
  * - `M` — the **Row** shape returned by reads (`find`, `findById`, `listen`).
@@ -406,16 +406,16 @@ export interface SDKCollectionClient<
 }
 
 /**
- * The unified data access object for the **admin CMS** (Entity-shaped).
+ * The unified data access object for the **admin admin** (Entity-shaped).
  *
  * Access collections as dynamic properties: `data.products.find(...)`. Each
  * accessor returns `Entity`-wrapped records (`{ id, path, values }`) — the
- * view-model the CMS renders. This is what `useData()` / the admin
+ * view-model the admin renders. This is what `useData()` / the admin
  * `RebaseContext.data` are backed by.
  *
  * @internal App developers do **not** use this — they use
  * {@link RebaseSdkData} (flat rows), which is what the SDK client and backend
- * `context.data` expose. This Entity-shaped map backs the admin CMS only.
+ * `context.data` expose. This Entity-shaped map backs the admin admin only.
  *
  * @group Data
  */
@@ -455,7 +455,7 @@ export type RebaseData<DB = unknown> = {
  *
  * Every accessor returns flat rows (the table's columns) via
  * {@link SDKCollectionClient} — access fields directly (`row.title`), never
- * `row.values.title`. The admin CMS uses {@link RebaseData} (Entity) instead.
+ * `row.values.title`. The admin uses {@link RebaseData} (Entity) instead.
  *
  * @example
  * // Frontend SDK

package/src/types/collections.ts

@@ -404,7 +404,6 @@ export type CollectionConfig<M extends Record<string, unknown> = Record<string,
  *
  * @group Models
  */
-// eslint-disable-next-line @typescript-eslint/no-explicit-any
 export type AnyCollectionConfig = CollectionConfig<any, any>;
 
 /**

package/src/types/data_source.ts

@@ -4,7 +4,7 @@ import { ALL_WHERE_FILTER_OPS, WhereFilterOp } from "./filter-operators";
  * Describes the capabilities and features supported by a data source (driver).
  *
  * Each driver (Postgres, Firebase, MongoDB, etc.) declares which features it
- * supports. The CMS uses this descriptor to:
+ * supports. The admin uses this descriptor to:
  * - Show/hide editor tabs (e.g. Relations for SQL, Subcollections for Firebase)
  * - Filter the property type picker (e.g. `relation` for SQL, `reference` for Firebase)
  * - Toggle driver-specific form controls (e.g. `columnType` for SQL)

package/src/types/database_adapter.ts

@@ -119,17 +119,22 @@ export interface DatabaseAdapterInitConfig {
     /** The shared collection registry to register into. */
     collectionRegistry: CollectionRegistryInterface;
     /**
-     * How the server is being run — see `RebaseBackendConfig.mode`.
+     * Whether this driver should describe its own schema.
      *
-     * In `"baas"` mode `collections` is empty by design: a driver that can
-     * describe its own schema should introspect the database and report the
-     * collections it found back on `InitializedDriver.collections`. Drivers
-     * that cannot introspect may ignore this.
+     * True when the project declared no collections, so there is nothing to
+     * serve unless the driver reads the live database and reports what it found
+     * on `InitializedDriver.collections`. Drivers that cannot introspect may
+     * ignore it — `initializeRebaseBackend` fails the boot with their name
+     * rather than serving nothing.
+     *
+     * This was a `mode: "cms" | "baas"` flag, which was never independent of
+     * `collections`: every consumer already required the list to be empty
+     * before acting on it, so the flag could only ever agree or contradict.
      */
-    mode?: "cms" | "baas";
+    introspectCollections?: boolean;
     /**
-     * `baas`-mode options — see `RebaseBackendConfig.baas`. Drivers that
-     * introspect should honour `unprotectedTables`.
+     * Options for an introspecting driver — see `RebaseBackendConfig.baas`.
+     * Drivers that introspect should honour `unprotectedTables`.
      */
     baas?: { unprotectedTables?: "exclude" | "serve" };
 }

package/src/types/entity_callbacks.ts

@@ -85,7 +85,7 @@ export interface AfterReadProps<M extends Record<string, unknown> = Record<strin
     collection: CollectionConfig<M>;
 
     /**
-     * Full path of the CMS where this collection is being fetched.
+     * Full path of the admin where this collection is being fetched.
      * Might contain unresolved aliases.
      */
     path: string;
@@ -132,7 +132,7 @@ export interface AfterSaveProps<M extends Record<string, unknown> = Record<strin
     collection: CollectionConfig<M>;
 
     /**
-     * Full path of the CMS where this entity is being saved.
+     * Full path of the admin where this entity is being saved.
      * Might contain unresolved aliases.
      */
     path: string;