bunderstack 0.24.0 → 0.24.2

package/llms.txt

@@ -41,9 +41,10 @@ MINIMAL APP
 
 The blueprint imports the backend declaration and never starts the runtime.
 Database adapters are imported from their own entry points: libsql(),
-pglite(), bunSql(), postgresJs(). Provisioning: `await provision(app)` pushes
-the schema in development and applies committed migrations once a migrations/
-folder exists.
+pglite(), bunSql(), postgresJs(). Production provisioning imports
+`provision(app)` from `bunderstack/provision` and requires committed migrations;
+that entrypoint never imports Drizzle Kit. Development schema push imports the
+same function name from `bunderstack/provision-schema` instead.
 
 DECLARING AN API
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bunderstack",
-  "version": "0.24.0",
+  "version": "0.24.2",
   "description": "Batteries-included backend framework for Bun: type-safe oRPC APIs, auth, storage, realtime, jobs, messaging, and validated env from one declaration.",
   "keywords": [
     "backend",
@@ -77,6 +77,10 @@
       "types": "./dist/provision.d.ts",
       "default": "./dist/provision.js"
     },
+    "./provision-schema": {
+      "types": "./dist/provision-schema.d.ts",
+      "default": "./dist/provision-schema.js"
+    },
     "./testing": {
       "types": "./dist/testing.d.ts",
       "default": "./dist/testing.js"

package/skills/creating-bunderstack-apps/references/verification.md

@@ -17,9 +17,10 @@ the configured Bunderstack entry. Set `package.json#bunderstack.entry` when the
 entry is not `src/bunderstack.ts`. `bun run blueprint:check` must pass in CI so
 the committed declaration matches the application.
 
-Before production, generate and commit the Drizzle `migrations/` folder. With
-no migrations folder, `provision(app)` uses the development schema-push loop
-(and needs drizzle-kit). Once migrations are committed, it applies pending
-migrations without importing drizzle-kit. Keep the generated migrations,
-blueprint, tests, worker entry, API mount, and deployment scripts under version
-control; never commit secrets, databases, uploads, or build output.
+Before production, generate and commit the Drizzle `migrations/` folder.
+`provision(app)` from `bunderstack/provision` only applies committed
+migrations and never imports drizzle-kit. For the local schema-push loop, import
+`provision` from `bunderstack/provision-schema`; that development-only
+entrypoint requires drizzle-kit. Keep the generated migrations, blueprint,
+tests, worker entry, API mount, and deployment scripts under version control;
+never commit secrets, databases, uploads, or build output.

package/skills/migrating-to-bunderstack/SKILL.md

@@ -55,25 +55,26 @@ export type App = typeof app
 
 All Bunderstack capabilities are imported directly from single-segment subpaths of `bunderstack`:
 
-| Subpath Import             | Purpose                                                                               |
-| -------------------------- | ------------------------------------------------------------------------------------- |
-| `bunderstack`              | Core backend builder (`bunderstack`, `defineApi`, `defineAccess`, `BunderstackError`) |
-| `bunderstack/libsql`       | libSQL / SQLite database adapter                                                      |
-| `bunderstack/postgres-js`  | postgres.js database adapter                                                          |
-| `bunderstack/bun-sql`      | `Bun.sql` Postgres adapter                                                            |
-| `bunderstack/pglite`       | PGlite in-memory / embedded Postgres adapter                                          |
-| `bunderstack/client`       | Framework-neutral typed client & `createLiveView`                                     |
-| `bunderstack/client-react` | React LiveView hook (`useLiveView`)                                                   |
-| `bunderstack/client-rest`  | Type-safe REST client                                                                 |
-| `bunderstack/query`        | TanStack Query integration (`createClient`, `syncRealtime`)                           |
-| `bunderstack/query-react`  | React-specific query helpers                                                          |
-| `bunderstack/sync`         | TanStack DB realtime sync collections                                                 |
-| `bunderstack/start`        | TanStack Start integration (`createApiHandlers`)                                      |
-| `bunderstack/start-auth`   | Better Auth client for TanStack Start                                                 |
-| `bunderstack/provision`    | Database schema provisioning (`provision(app)`)                                       |
-| `bunderstack/testing`      | Test fixture helpers                                                                  |
-| `bunderstack/schema`       | Internal system tables (`export * from 'bunderstack/schema'`)                         |
-| `bunderstack/typeid`       | TypeID column types & generators                                                      |
+| Subpath Import                 | Purpose                                                                               |
+| ------------------------------ | ------------------------------------------------------------------------------------- |
+| `bunderstack`                  | Core backend builder (`bunderstack`, `defineApi`, `defineAccess`, `BunderstackError`) |
+| `bunderstack/libsql`           | libSQL / SQLite database adapter                                                      |
+| `bunderstack/postgres-js`      | postgres.js database adapter                                                          |
+| `bunderstack/bun-sql`          | `Bun.sql` Postgres adapter                                                            |
+| `bunderstack/pglite`           | PGlite in-memory / embedded Postgres adapter                                          |
+| `bunderstack/client`           | Framework-neutral typed client & `createLiveView`                                     |
+| `bunderstack/client-react`     | React LiveView hook (`useLiveView`)                                                   |
+| `bunderstack/client-rest`      | Type-safe REST client                                                                 |
+| `bunderstack/query`            | TanStack Query integration (`createClient`, `syncRealtime`)                           |
+| `bunderstack/query-react`      | React-specific query helpers                                                          |
+| `bunderstack/sync`             | TanStack DB realtime sync collections                                                 |
+| `bunderstack/start`            | TanStack Start integration (`createApiHandlers`)                                      |
+| `bunderstack/start-auth`       | Better Auth client for TanStack Start                                                 |
+| `bunderstack/provision`        | Production provisioning from committed migrations                                     |
+| `bunderstack/provision-schema` | Development-only schema push through Drizzle Kit                                      |
+| `bunderstack/testing`          | Test fixture helpers                                                                  |
+| `bunderstack/schema`           | Internal system tables (`export * from 'bunderstack/schema'`)                         |
+| `bunderstack/typeid`           | TypeID column types & generators                                                      |
 
 ---
 
@@ -387,11 +388,12 @@ throw new BunderstackError('FORBIDDEN', 'Quota exceeded')
 ### Development vs. Production Lifecycle
 
 1. **Local Development (No Migrations Folder):**
-   - In dev, `await provision(app)` automatically pushes the schema to the SQLite/libSQL/Postgres database.
+   - Import `provision` from `bunderstack/provision-schema`; it pushes the schema to the SQLite/libSQL/Postgres database.
    - Developers can rapidly prototype and iterate on table schemas without generating migrations on every change.
 
 2. **Production & Bunderhost Deployments (MANDATORY Migrations):**
    - **Committed migrations are strictly mandatory for production deployments.**
+   - Import `provision` from `bunderstack/provision`; it contains no Drizzle Kit import edge and fails clearly when the migration journal is missing.
    - Bunderhost will **NOT** run schema push in production; deployment will fail if committed migrations in `migrations/` are missing or out of date.
 
 ### CRITICAL MIGRATION RULES

package/skills/migrating-to-bunderstack/references/runtime-replacements.md

@@ -255,9 +255,10 @@ with names and safe placeholders only.
 
 ## Provisioning, migrations, and blueprint
 
-`provision(app)` uses the development schema-push loop while no `migrations/`
-folder exists, and applies committed migrations once one does. Generate and
-commit migrations before production:
+`provision(app)` from `bunderstack/provision` applies committed migrations
+without importing Drizzle Kit and fails when the journal is absent. During
+local prototyping, import it from `bunderstack/provision-schema` to use the
+development schema-push loop. Generate and commit migrations before production:
 
 ```json
 {