@getstrata/starter 2.2.60 → 3.0.5
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 +12 -0
- package/dist/cli.js +2087 -1636
- package/dist/templates/overlays/spa-react/frontend/src/examples/notes.ts +4 -7
- package/dist/templates/package.json +3 -3
- package/dist/templates/src/bootstrap/preload.ts +0 -4
- package/dist/templates/src/bootstrap/providers/cache.ts +11 -29
- package/dist/templates/src/bootstrap/providers/storage.ts +9 -9
- package/dist/templates/src/bootstrap/server.ts +13 -32
- package/dist/templates/src/modules/site/index.ts +4 -7
- package/dist/templates/src/routes.ts +6 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,6 +14,12 @@ This package ships the same generator at the same version and also works directl
|
|
|
14
14
|
bunx @getstrata/starter my-app
|
|
15
15
|
```
|
|
16
16
|
|
|
17
|
+
## Generation safety and feature plan
|
|
18
|
+
|
|
19
|
+
Generation validates a frozen feature plan before creating output. Unsupported raw combinations (such as RLS with SQLite or MFA without cookie authentication) fail before files are emitted. Interactive and CLI choices normalize through the installer first. The generated `strata.features.json` records requirements, derived capabilities, required feature artifacts, and a complete emitted file inventory.
|
|
20
|
+
|
|
21
|
+
Existing output paths are always rejected, including with `--force`; choose a new path. A failed generation removes only the output directory acquired by that attempt so it can be retried.
|
|
22
|
+
|
|
17
23
|
## Usage
|
|
18
24
|
|
|
19
25
|
```bash
|
|
@@ -43,3 +49,9 @@ Discover registered commands with `bunx strata help`. `dev` and `start` run HTTP
|
|
|
43
49
|
- [Getting started](https://github.com/EyK-26/strata/blob/main/docs/GETTING-STARTED.md)
|
|
44
50
|
- [Starter and layers](https://github.com/EyK-26/strata/blob/main/docs/STARTER.md)
|
|
45
51
|
- [Building apps](https://github.com/EyK-26/strata/blob/main/docs/BUILDING-APPS.md)
|
|
52
|
+
|
|
53
|
+
## Work tracker reference
|
|
54
|
+
|
|
55
|
+
The programmatic generator accepts `reference: "work-tracker"` alongside user authentication and tenant isolation. It emits the same organization/member/project/task domain for cookie/server and token/API applications. Owners manage memberships and projects, members create and complete tasks, and viewers read. `/work` provides cookie-authenticated forms with CSRF protection; `/api/v1/work` exposes the shared workflow for API clients. An authenticated request supplies the tenant and actor; payload fields cannot override them.
|
|
56
|
+
|
|
57
|
+
Every accepted mutation writes a durable audit record and publishes through the framework SQL outbox inside the same transaction. The included `work.notification` listener records delivery idempotently; run the ordinary outbox worker to consume pending events. The reference uses explicit tenant predicates and composite foreign keys on every driver, and adds PostgreSQL RLS policies when selected. This is a bounded reference workflow, not a complete project-management product.
|