Bun
Possible, a medium change. A context is one workspace package plus a small contract package.
The files
Explorer
- package.jsonworkspaces: contexts/* and contexts/*/contract
- index.tsapi, worker, migrate
- contexts.tsgeneratednot committed
- gen.tsfinds the folders
- boundaries.tsguards layers and contexts
- context.yaml
- package.json
- register.ts
- policies.yaml
- flags.yaml
What the tools allow
| Question | Answer | Tag |
|---|---|---|
| Tests inside, with SIT | yes: 37 pass | MEASURED |
| A planted failing test | fails | MEASURED |
| Tests or docs in the Docker image | 0 found | MEASURED |
| Restart after an edit | 254 ms | MEASURED |
| Restart after a test edit | none | MEASURED |
Adding a context
a third context (real output, shortened)
$scripts/new-context.sh third
$
1 / 4
What changes in the template
| Change | Count | Tag |
|---|---|---|
| Files moved, consumer template | 42 of 409 | MEASURED |
| Root configs edited | 6 | MEASURED |
| Package files per context | 2 | MEASURED |
| New kernel and tool code | 1,693 lines | MEASURED |
What does not work cleanly
- Two new contexts conflict in
bun.lock, one hunk.bun installfixes it. MEASURED merge=unionon that file is unsafe: the frozen install then fails. MEASURED- No linter keeps IO out of the domain, so a 150-line checker does. MEASURED