create-bw-app 0.27.7 → 0.27.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -18,7 +18,7 @@ The workspace wrapper delegates to this package with `workspace:*` dependency wi
|
|
|
18
18
|
|
|
19
19
|
## Published usage
|
|
20
20
|
|
|
21
|
-
|
|
21
|
+
Use the published package from npm:
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
24
|
pnpm dlx create-bw-app
|
|
@@ -40,7 +40,7 @@ bw admin create --email owner@example.com
|
|
|
40
40
|
- `bw add <moduleKey>` resolves requirements, installs thin package mounts and module wiring, and appends migrations.
|
|
41
41
|
- `bw upgrade [moduleKey]` includes the existing managed update flow plus forward-only module migrations. For a staged database rollout, `bw upgrade <moduleKey> --through-migration <filename>` still updates packages and managed files but appends and records that module only through the named migration.
|
|
42
42
|
- Destructive migrations are held at the preceding safe boundary. After compatible code is deployed and affected data is backed up, apply a held migration with an explicit module-scoped `bw upgrade <moduleKey> --include-destructive-migrations`. A destructive `--through-migration` target also requires that opt-in.
|
|
43
|
-
- `bw doctor` checks package, config, scaffold, environment-name, migration, configured function-region, and deployed function-region consistency. App-owned scaffold files are preserved on upgrade; doctor warns when their recorded template baseline is outdated and their contents differ from the current template. Use `bw diff`, reconcile relevant changes, and verify behavior before recording the reviewed baseline with `bw scaffold manage <path>` followed by `bw scaffold own <path>` (neither replaces file contents). Live database objects, applied migrations, and authenticated permissions are explicitly **NOT VERIFIED** by doctor; a successful local result does not certify deployed behavior. Pass `--deployment-url` to inspect the deployed `x-vercel-id`; add `--report` to stamp the result in the app manifest.
|
|
43
|
+
- `bw doctor` checks exact BrightWeb package and lockfile provenance, config, scaffold, environment-name, migration content and provenance, configured function-region, and deployed function-region consistency. Exact package provenance requires installed dependencies and a pnpm lockfile; migration provenance verifies compatible headers, source filenames, cursors, and SHA-256 content. App-owned scaffold files are preserved on upgrade; doctor warns when their recorded template baseline is outdated and their contents differ from the current template. Use `bw diff`, reconcile relevant changes, and verify behavior before recording the reviewed baseline with `bw scaffold manage <path>` followed by `bw scaffold own <path>` (neither replaces file contents). Live database objects, applied migrations, and authenticated permissions are explicitly **NOT VERIFIED** by doctor; a successful local result does not certify deployed behavior. Pass `--deployment-url` to inspect the deployed `x-vercel-id`; add `--report` to stamp the result in the app manifest.
|
|
44
44
|
- `bw admin create --email <email>` creates a passwordless Supabase Auth user, transactionally ensures its profile and `admin` assignment, then sends the Core Auth `/reset-password` flow. It always refuses when the project already has an admin (use the in-app admin role controls to add administrators) and never promotes an existing Auth user.
|
|
45
45
|
- All mutating commands support `--dry-run`.
|
|
46
46
|
|
|
@@ -82,7 +82,7 @@ Current updater behavior:
|
|
|
82
82
|
- writes `package.json`, `next.config.ts`, `.gitignore`, and `README.md` for both templates
|
|
83
83
|
- 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
|
|
84
84
|
- site apps also write `AGENTS.md`, `docs/ai/README.md`, `docs/ai/examples.md`, and `docs/ai/app-context.json` for app-local AI handoff
|
|
85
|
-
- supports repo-local `workspace:*` wiring and
|
|
85
|
+
- supports repo-local `workspace:*` wiring and published semver dependency wiring
|
|
86
86
|
- writes `.brightweb/app-manifest.json` as the machine-authoritative scaffold and module record
|
|
87
87
|
|
|
88
88
|
## Workspace mode extras
|