create-bw-app 0.9.6 → 0.9.7

package/README.md

@@ -57,7 +57,7 @@ Current updater behavior:
 - copies a clean Next.js App Router starter template
 - platform apps include BrightWeb auth, shell wiring, and optional module starter surfaces
 - platform apps include a local `components/` folder for app-owned UI alongside the shared BrightWeb packages
-- platform apps in published mode also write `supabase/module-registry.json`, `supabase/clients/<slug>/stack.json`, and the resolved shared SQL migrations under `supabase/modules/<module>/migrations`
+- platform apps in published mode also write `supabase/config.toml`, a CLI-ready flat `supabase/migrations/` folder, `supabase/module-registry.json`, `supabase/clients/<slug>/stack.json`, and the resolved shared SQL migrations under `supabase/modules/<module>/migrations`
 - site apps include Next.js, Tailwind CSS v4, and local component primitives
 - writes `package.json`, `next.config.ts`, `.gitignore`, and `README.md` for both templates
 - platform apps also write `.env.local`, `AGENTS.md`, `docs/ai/README.md`, `docs/ai/examples.md`, `docs/ai/app-context.json`, and generated config files for brand and module state

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "create-bw-app",
   "private": false,
-  "version": "0.9.6",
+  "version": "0.9.7",
   "type": "module",
   "bin": "bin/create-bw-app.mjs",
   "files": [

package/src/generator.mjs

@@ -914,6 +914,24 @@ export async function ensureDirectory(targetDir) {
   await fs.mkdir(targetDir, { recursive: true });
 }
 
+function createGeneratedSupabaseConfig(projectId) {
+  return [
+    `project_id = "${projectId}"`,
+    "",
+    "[db]",
+    "major_version = 17",
+    "",
+    "[db.migrations]",
+    "enabled = true",
+    'schema_paths = []',
+    "",
+    "[db.seed]",
+    "enabled = false",
+    'sql_paths = []',
+    "",
+  ].join("\n");
+}
+
 function createScopedDbModuleRegistry(registry, moduleKeys) {
   return {
     modules: Object.fromEntries(
@@ -965,6 +983,35 @@ async function writeClientStack(baseRoot, slug, dbInstallPlan, options = {}) {
   );
 }
 
+async function writeSupabaseCliMigrations({ targetDir, dbInstallPlan }) {
+  const targetSupabaseDir = path.join(targetDir, "supabase");
+  const targetMigrationsDir = path.join(targetSupabaseDir, "migrations");
+
+  await ensureDirectory(targetMigrationsDir);
+  await fs.writeFile(path.join(targetSupabaseDir, "config.toml"), createGeneratedSupabaseConfig(path.basename(targetDir)), "utf8");
+
+  let sequence = 1;
+  for (const moduleKey of dbInstallPlan.resolvedOrder) {
+    const sourceModuleDir = path.join(TEMPLATE_SUPABASE_ROOT, "modules", moduleKey, "migrations");
+    if (!(await pathExists(sourceModuleDir))) {
+      continue;
+    }
+
+    const fileNames = (await fs.readdir(sourceModuleDir))
+      .filter((fileName) => fileName.endsWith(".sql"))
+      .sort();
+
+    for (const fileName of fileNames) {
+      const targetFileName = `${String(sequence).padStart(4, "0")}_${moduleKey}__${fileName}`;
+      await fs.copyFile(
+        path.join(sourceModuleDir, fileName),
+        path.join(targetMigrationsDir, targetFileName),
+      );
+      sequence += 1;
+    }
+  }
+}
+
 async function writeBundledSupabaseBaseline({ targetDir, slug, dbInstallPlan, registry }) {
   const shippedModuleKeys = dbInstallPlan.resolvedOrder;
   if (shippedModuleKeys.length === 0) {
@@ -995,6 +1042,7 @@ async function writeBundledSupabaseBaseline({ targetDir, slug, dbInstallPlan, re
   }
 
   await writeClientStack(targetDir, slug, dbInstallPlan);
+  await writeSupabaseCliMigrations({ targetDir, dbInstallPlan });
 }
 
 export async function runInstall(command, cwd) {

package/template/supabase/README.md

@@ -1,16 +1,18 @@
 # Brightweb Supabase Structure
 
-This directory is the canonical home for the Brightweb database baseline and its forward migrations.
+This directory is the scaffold-owned home for the Brightweb shared database module baselines and forward migrations that were selected for this project.
 
 ## Directory map
 
 - `module-registry.json`: shared module dependency graph and migration source paths
+- `config.toml`: standard Supabase CLI config for this project
+- `migrations/*.sql`: CLI-ready ordered migrations for `supabase db push`
 - `modules/core`: always-on platform foundations
 - `modules/admin`: RBAC and privileged governance behavior
 - `modules/crm`: organizations, CRM contacts, and invitation flows
 - `modules/projects`: project and work-management data
 - `clients/<client-slug>`: true client-only schema deltas plus the client stack plan
-- `.generated/<client-slug>`: materialized Supabase workdirs produced by `pnpm db:materialize`
+- `clients/<client-slug>`: client stack metadata and client-only migrations for this project
 
 ## Ownership rule
 
@@ -20,9 +22,9 @@ Shared database changes should be authored by ownership area, not by client app:
 - shared module migrations are applied only when that module is enabled for the client
 - client-specific migrations are the exception, not the default
 
-In workspace scaffold mode, `create-bw-app` writes `supabase/clients/<slug>/stack.json` so the generated app modules and the database install plan stay aligned.
+`create-bw-app` writes `supabase/clients/<slug>/stack.json` so the generated app modules and the database install plan stay aligned.
 
-The module baselines in this repo are the canonical Brightweb v1 install path. Future schema work should extend them with forward migrations instead of carrying historical cleanup sequences.
+These module baselines are the project-local Brightweb install path for the selected stack. Future schema work should extend them with forward migrations instead of carrying historical cleanup sequences.
 
 Maintainer references:
 
@@ -47,23 +49,9 @@ Create a client-only migration:
 pnpm db:new client:acme bespoke_reporting_table
 ```
 
-Print the effective apply order for a client:
+The shipped `module-registry.json` records the shared module dependency graph for this project.
 
-```bash
-pnpm db:plan acme
-```
-
-Materialize an installable Supabase workdir for a client stack:
-
-```bash
-pnpm db:materialize acme
-```
-
-This writes a generated workdir under `supabase/.generated/<client-slug>` with:
-
-- ordered migrations merged from `core`, enabled modules, and client-only deltas
-- a generated `config.toml`
-- a `manifest.json` showing the source file for each materialized migration
+Projects created from the published scaffold should use the Supabase files in this folder directly. `supabase/migrations/*.sql` is the flat ordered layout that Supabase CLI reads, while `supabase/modules/*/migrations` remains the project-local modular source layout. Repo-level `db:materialize` is a deprecated Brightweb workspace compatibility command and is not the intended workflow for standalone generated apps.
 
 ## Related READMEs