@gusto/create-baerly-storage 0.5.0 → 0.7.0

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.
Files changed (37) hide show
  1. package/dist/THIRD-PARTY-LICENSES.txt +204 -0
  2. package/dist/index.js +1537 -145
  3. package/dist/index.js.map +1 -1
  4. package/dist/templates/addons/docker/Dockerfile +13 -11
  5. package/dist/templates/minimal-cloudflare/AGENTS.md +77 -399
  6. package/dist/templates/minimal-cloudflare/README.md +33 -97
  7. package/dist/templates/minimal-cloudflare/package.json +12 -9
  8. package/dist/templates/minimal-cloudflare/pnpm-workspace.yaml +13 -7
  9. package/dist/templates/minimal-cloudflare/tsconfig.app.json +2 -3
  10. package/dist/templates/minimal-cloudflare/tsconfig.worker.json +2 -3
  11. package/dist/templates/minimal-cloudflare/vitest.config.ts +1 -1
  12. package/dist/templates/minimal-cloudflare/wrangler.jsonc +4 -2
  13. package/dist/templates/minimal-node/AGENTS.md +80 -380
  14. package/dist/templates/minimal-node/README.md +37 -135
  15. package/dist/templates/minimal-node/package.json +11 -9
  16. package/dist/templates/minimal-node/pnpm-workspace.yaml +14 -9
  17. package/dist/templates/minimal-node/tsconfig.app.json +2 -3
  18. package/dist/templates/minimal-node/tsconfig.server.json +2 -3
  19. package/dist/templates/react-cloudflare/AGENTS.md +101 -444
  20. package/dist/templates/react-cloudflare/README.md +14 -54
  21. package/dist/templates/react-cloudflare/package.json +18 -15
  22. package/dist/templates/react-cloudflare/pnpm-workspace.yaml +13 -7
  23. package/dist/templates/react-cloudflare/tsconfig.app.json +2 -3
  24. package/dist/templates/react-cloudflare/tsconfig.worker.json +2 -3
  25. package/dist/templates/react-cloudflare/vitest.config.ts +1 -1
  26. package/dist/templates/react-cloudflare/wrangler.jsonc +4 -2
  27. package/dist/templates/react-node/AGENTS.md +108 -474
  28. package/dist/templates/react-node/README.md +35 -125
  29. package/dist/templates/react-node/package.json +16 -14
  30. package/dist/templates/react-node/pnpm-workspace.yaml +14 -9
  31. package/dist/templates/react-node/tsconfig.app.json +2 -3
  32. package/dist/templates/react-node/tsconfig.server.json +2 -3
  33. package/package.json +7 -7
  34. package/dist/templates/minimal-cloudflare/uint8array-base64.d.ts +0 -16
  35. package/dist/templates/minimal-node/uint8array-base64.d.ts +0 -16
  36. package/dist/templates/react-cloudflare/uint8array-base64.d.ts +0 -16
  37. package/dist/templates/react-node/uint8array-base64.d.ts +0 -16
@@ -1,31 +1,14 @@
1
1
  # minimal-node
2
2
 
3
- A baerly-storage app scaffolded with `@gusto/create-baerly-storage` for
4
- the **Node** target — any host that runs `node server.js` (Railway,
5
- Render, Fly without Docker, Heroku, a VM, a container scheduler, your
6
- laptop). Runs zero-config on local filesystem storage out of the box;
7
- promote to an S3-compatible bucket via `@gusto/baerly-storage/node` for
8
- production. AWS S3 and Cloudflare R2 are the production-supported
9
- targets; MinIO is the local conformance target, and other endpoints
10
- require `baerly doctor --bucket` plus owner validation. Ships
11
- `auth: "none"` so the day-1 happy path works with zero env vars; flip
12
- to a shared secret or wire `bearerJwt` against your OIDC IdP before
13
- deploy — see "Going to production" below.
14
-
15
- **In production, the S3-compatible bucket is the durable state**
16
- (locally, a `./.baerly-data` directory stands in). The Node process is
17
- trusted app code with bucket credentials; it applies the
18
- baerly-storage protocol, but it is not a database server. No daemon,
19
- lock table, scheduler, or idle database bill; maintenance is automatic
20
- and write-triggered.
21
-
22
- To ship a production Dockerfile alongside, scaffold with
23
- `--with=docker` — the add-on writes a multi-stage distroless Dockerfile,
24
- `.dockerignore`, and `healthcheck.js` into this same shape.
3
+ A baerly-storage app scaffolded with `@gusto/create-baerly-storage` for the **Node** target — any host that runs `node server.js` (Railway, Render, Fly without Docker, Heroku, a VM, a container scheduler, your laptop). Runs zero-config on local filesystem storage out of the box; promote to an S3-compatible bucket via `@gusto/baerly-storage/node` for production. AWS S3 and Cloudflare R2 are the production-supported targets; MinIO is the local conformance target, and other endpoints require `baerly doctor --bucket` plus owner validation. Ships `auth: "none"` so the day-1 happy path works with zero env vars; flip to a shared secret or wire `bearerJwt` against your OIDC IdP before deploy — see "Going to production" below.
4
+
5
+ **In production, the S3-compatible bucket is the durable state** (locally, a `./.baerly-data` directory stands in). The Node process is trusted app code with bucket credentials; it applies the baerly-storage protocol, but it is not a database server. No daemon, lock table, scheduler, or idle database bill; maintenance is automatic and write-triggered.
6
+
7
+ To ship a production Dockerfile alongside, scaffold with `--with=docker` — the add-on writes a multi-stage distroless Dockerfile, `.dockerignore`, and `healthcheck.js` into this same shape.
25
8
 
26
9
  ## What you got
27
10
 
28
- ```
11
+ ```text
29
12
  minimal-node/
30
13
  ├── package.json # one package, all deps
31
14
  ├── tsconfig.json # project-references stub
@@ -35,7 +18,7 @@ minimal-node/
35
18
  ├── index.html # SPA shell — Vite's entry point
36
19
  ├── .env.example # storage selection (local-fs default) + PORT
37
20
  ├── baerly.config.ts # app, tenant, target, domain
38
- ├── AGENTS.md # deeper guide: predicates, schemas,
21
+ ├── AGENTS.md # deeper guide: where the API docs are,
39
22
  │ # auth recipes, graduation
40
23
  ├── src/
41
24
  │ ├── server/
@@ -52,26 +35,16 @@ pnpm install
52
35
  pnpm dev
53
36
  ```
54
37
 
55
- `pnpm dev` runs `vite`. `baerlyDev()` from `@gusto/baerly-storage/dev/vite`
56
- mounts the Node HTTP listener as Connect middleware on the same Vite
57
- process that serves the SPA, so `GET /` hits the SPA on
58
- `http://localhost:5173/` and anything baerly-storage handles (e.g.
59
- `GET /v1/healthz`) is served on the same origin — one process, one
60
- port, SPA + HMR + `/v1/*` in one command. Storage is `LocalFsStorage`
61
- rooted at `.baerly-data/`, so first-touch needs no S3 creds, no JWKS,
62
- and no second process.
38
+ `pnpm dev` runs `vite`. `baerlyDev()` from `@gusto/baerly-storage/dev/vite` mounts the Node HTTP listener as Connect middleware on the same Vite process that serves the SPA, so `GET /` hits the SPA on `http://localhost:5173/` and anything baerly-storage handles (e.g. `GET /v1/healthz`) is served on the same origin — one process, one port, SPA + HMR + `/v1/*` in one command. Storage is `LocalFsStorage` rooted at `.baerly-data/`, so first-touch needs no S3 creds, no JWKS, and no second process.
63
39
 
64
- For production-shaped local runs (the built SPA served from
65
- `dist/client/` alongside `/v1/*`):
40
+ For production-shaped local runs (the built SPA served from `dist/client/` alongside `/v1/*`):
66
41
 
67
42
  ```sh
68
43
  pnpm build
69
44
  pnpm start
70
45
  ```
71
46
 
72
- `pnpm start` defaults to `localFsStorage()` (persists to
73
- `./.baerly-data`, zero credentials, single-node only). To opt into
74
- S3 or R2:
47
+ `pnpm start` defaults to `localFsStorage()` (persists to `./.baerly-data`, zero credentials, single-node only). To opt into S3 or R2:
75
48
 
76
49
  ```sh
77
50
  # AWS S3
@@ -81,103 +54,45 @@ BUCKET=... AWS_ACCESS_KEY_ID=... AWS_SECRET_ACCESS_KEY=... pnpm start
81
54
  R2_ACCOUNT_ID=... BUCKET=... AWS_ACCESS_KEY_ID=... AWS_SECRET_ACCESS_KEY=... pnpm start
82
55
  ```
83
56
 
84
- The server reads `BUCKET`, `AWS_ACCESS_KEY_ID`,
85
- `AWS_SECRET_ACCESS_KEY` at startup; when those are absent it falls
86
- back to `localFsStorage()` for local runs. **In a detected deployment
87
- (`NODE_ENV=production` or a known PaaS) it refuses to start and requires
88
- a bucket** — local-fs is local-dev only (single-process, no
89
- cross-process CAS or crash durability). The default `auth: "none"`
90
- posture needs no auth env vars. The default entrypoint also reads
91
- optional `AWS_REGION` and `PORT`. There is no `WEB_ROOT` env var — the SPA
92
- path is the hard-coded `webRoot: "dist/client"` in
93
- `src/server/index.ts`. Auth, tenant, and maintenance env vars require
94
- adopting the documented code/config recipe first.
95
-
96
- Maintenance (compaction + GC) is automatic and in-band: it runs
97
- inline on the rare write that crosses a maintenance trigger — no env
98
- var, no tick, no `setInterval`, no operator scheduler. Two ops-plane
99
- env vars tune it: `BAERLY_MAINTENANCE_MAX_FOLD_BYTES` raises the
100
- snapshot ceiling and `BAERLY_MAINTENANCE_DISABLE=1` is a kill switch.
101
- For an explicit out-of-band sweep, call `runScheduledMaintenance`
102
- from `@gusto/baerly-storage`.
103
-
104
- After `pnpm build`, `pnpm start` serves the Vite-built SPA from
105
- `dist/client/` on `http://localhost:8080/` and the baerly-storage HTTP
106
- surface on `http://localhost:8080/v1/*` — single origin, no CORS.
107
-
108
- `pnpm typecheck` runs `tsc -b --noEmit` across both project
109
- references.
57
+ The server reads `BUCKET`, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` at startup; when those are absent it falls back to `localFsStorage()` for local runs. **In a detected deployment (`NODE_ENV=production` or a known PaaS) it refuses to start and requires a bucket** — local-fs is local-dev only (single-process, no cross-process CAS or crash durability). The default `auth: "none"` posture needs no auth env vars. The default entrypoint also reads optional `AWS_REGION` and `PORT`. There is no `WEB_ROOT` env var — the SPA path is the hard-coded `webRoot: "dist/client"` in `src/server/index.ts`. Auth, tenant, and maintenance env vars require adopting the documented code/config recipe first.
58
+
59
+ Maintenance (compaction + GC) is automatic and in-band: it runs inline on the rare write that crosses a maintenance trigger — no env var, no tick, no `setInterval`, no operator scheduler. Two ops-plane env vars tune it: `BAERLY_MAINTENANCE_MAX_FOLD_BYTES` raises the snapshot ceiling and `BAERLY_MAINTENANCE_DISABLE=1` is a kill switch. For an explicit out-of-band sweep, call `runScheduledMaintenance` from `@gusto/baerly-storage/maintenance`.
60
+
61
+ After `pnpm build`, `pnpm start` serves the Vite-built SPA from `dist/client/` on `http://localhost:8080/` and the baerly-storage HTTP surface on `http://localhost:8080/v1/*` — single origin, no CORS.
62
+
63
+ `pnpm typecheck` runs `tsc -b --noEmit` across both project references.
110
64
 
111
65
  ## Deploy
112
66
 
113
- This scaffold runs anywhere `node server.js` runs. The `package.json`
114
- exposes `build` (Vite SPA + TS check) and `start`
115
- (`node --experimental-strip-types src/server/index.ts`); arrange your
116
- host to run `pnpm install && pnpm build`, then `pnpm start` with the
117
- storage/auth env vars exported or configured in the process manager.
118
- A deployment must set a durable bucket (`BUCKET` + `AWS_*`, or
119
- `R2_ACCOUNT_ID` + creds); the server fails loud rather than running on
120
- local-fs, which is local-dev only. Self-hosting without a cloud bucket,
121
- run MinIO on the box or use SQLite + Litestream.
67
+ This scaffold runs anywhere `node server.js` runs. The `package.json` exposes `build` (Vite SPA + TS check) and `start` (`node src/server/index.ts`); arrange your host to run `pnpm install && pnpm build`, then `pnpm start` with the storage/auth env vars exported or configured in the process manager. A deployment must set a durable bucket (`BUCKET` + `AWS_*`, or `R2_ACCOUNT_ID` + creds); the server fails loud rather than running on local-fs, which is local-dev only. Self-hosting without a cloud bucket, run MinIO on the box or use SQLite + Litestream.
122
68
 
123
69
  Concrete shapes:
124
70
 
125
- - **Managed PaaS** (Railway, Render, DO App Platform, Fly Machines
126
- without a Dockerfile, Heroku): push the repo to a connected GitHub
127
- repo, set env vars from `.env.example` in the dashboard, deploy.
128
- The platform's buildpack detects Node and runs the root scripts.
129
- - **VM / bare-metal**: clone, install Node 24+, copy `.env.example`
130
- to `.env` as a template, then export those values or configure them
131
- in your process manager (Node does not load `.env` automatically).
132
- Run `pnpm install && pnpm build && pnpm start` under systemd, pm2,
133
- or your process manager of choice.
134
- - **Container** (Docker, k8s, ECS, Fly Machines with a Dockerfile):
135
- scaffold with `pnpm create @gusto/baerly-storage@latest my-app --target=node --with=docker` to add
136
- a production Dockerfile, `.dockerignore`, and `healthcheck.js`
137
- alongside this shape, then `docker build .`.
71
+ - **Managed PaaS** (Railway, Render, DO App Platform, Fly Machines without a Dockerfile, Heroku): push the repo to a connected GitHub repo, set env vars from `.env.example` in the dashboard, deploy. The platform's buildpack detects Node and runs the root scripts.
72
+ - **VM / bare-metal**: clone, install Node 26+, copy `.env.example` to `.env` as a template, then export those values or configure them in your process manager (Node does not load `.env` automatically). Run `pnpm install && pnpm build && pnpm start` under systemd, pm2, or your process manager of choice.
73
+ - **Container** (Docker, k8s, ECS, Fly Machines with a Dockerfile): scaffold with `pnpm create @gusto/baerly-storage@latest my-app --target=node --with=docker` to add a production Dockerfile, `.dockerignore`, and `healthcheck.js` alongside this shape, then `docker build .`.
138
74
 
139
75
  Verify: `curl https://<your-service>/v1/healthz`.
140
76
 
141
77
  ## Next steps
142
78
 
143
- 1. **Read `AGENTS.md`** for the agent-facing guide — predicates,
144
- indexes, schemas, auth recipes (JWKS setup), write-triggered
145
- maintenance, and the graduation criteria. (Claude Code
146
- users: `@gusto/create-baerly-storage` mirrors `AGENTS.md` to `CLAUDE.md` at
147
- scaffold time.)
148
- 2. **Declare your first collection schema** in `baerly.config.ts`
149
- via `defineConfig({ collections: { ... } })`. The Node adapter
150
- passes that config to `Db.create({ storage, app, tenant, config })`,
151
- so schema validation is live and bad inserts return 400.
152
- 3. **Set up production auth** — follow `AGENTS.md` → "Going to
153
- production". Pattern B flips `auth: "shared-secret"` and reads
154
- `SHARED_SECRET` from `process.env`; Pattern C wires `bearerJwt`
155
- against your OIDC IdP via an env-aware factory `verifier:`
156
- override (`JWKS_URL` + `JWT_ISSUER` + `JWT_AUDIENCE`).
157
- Verify the bucket with `baerly doctor --bucket=<s3-uri>` and the
158
- deployed service with `curl https://<your-service>/v1/healthz`.
79
+ 1. **Read `AGENTS.md`** for the agent-facing guide — pointers to the installed API docs (predicates, indexes, schemas), auth recipes (JWKS setup), write-triggered maintenance, and the graduation criteria. (Claude Code users: `@gusto/create-baerly-storage` mirrors `AGENTS.md` to `CLAUDE.md` at scaffold time.)
80
+ 2. **Declare your first collection schema** in `baerly.config.ts` via `defineConfig({ collections: { ... } })`. The Node adapter passes that config to `Db.create({ storage, app, tenant, config })`, so schema validation is live and bad inserts return 400.
81
+ 3. **Set up production auth** — follow `AGENTS.md` → "Going to production". Pattern B flips `auth: "shared-secret"` and reads `SHARED_SECRET` from `process.env`; Pattern C wires `bearerJwt` against your OIDC IdP via an env-aware factory `verifier:` override (`JWKS_URL` + `JWT_ISSUER` + `JWT_AUDIENCE`). Verify the bucket with `baerly doctor --bucket=<s3-uri>` and the deployed service with `curl https://<your-service>/v1/healthz`.
159
82
 
160
83
  ## When to graduate
161
84
 
162
- baerly-storage is designed for the small-to-medium operating point.
163
- Past these thresholds, S3 list-prefix latency and per-class operation
164
- pricing starts to dominate, and you've outgrown the workload envelope — move to a database service:
85
+ baerly-storage is designed for the small-to-medium operating point. Past these thresholds, S3 list-prefix latency and per-class operation pricing starts to dominate, and you've outgrown the workload envelope — move to a database service:
165
86
 
166
- - **~30 writes / minute / collection** — per-collection throughput estimate (CAS-livelock model)
167
- - **>10 GB / tenant** — R2 free-tier storage cost line (a billing signal, not a protocol ceiling)
168
- - **~100 collections / tenant** — soft fan-out guideline (linear cost, bench-grounded; nothing enforces it)
87
+ - **Writes per collection** — per-collection throughput estimate (CAS-livelock model)
88
+ - **Stored bytes per tenant** — R2 free-tier storage cost line (a billing signal, not a protocol ceiling)
89
+ - **Collections per tenant** — soft fan-out guideline (linear cost, bench-grounded; nothing enforces it)
169
90
 
170
- When you cross these signals, graduation is mechanical:
171
- `baerly export --target=postgres` walks your log entries (already Debezium-style CDC change events) into a database service. If your
172
- deploy target is Cloudflare Workers and you'll accept Cloudflare
173
- lock-in, [D1](https://developers.cloudflare.com/d1/) is cheaper
174
- per-write at M-size and is a natural next step. If you're on
175
- AWS, on-prem, or want your data portable, managed Postgres is
176
- the typical destination. Either way — graduation is a Baerly win,
177
- not a churn event.
91
+ The figures for each line live in docs/spec/scale-ceilings.md § "The published envelope" in the baerly-storage repo.
178
92
 
179
- **Export to a database service** (swap `--target=` for `sqlite`,
180
- `postgres`, or `d1`):
93
+ When you cross these signals, graduation is mechanical: `baerly export --target=postgres` walks your log entries (already Debezium-style CDC change events) into a database service. If your deploy target is Cloudflare Workers and you'll accept Cloudflare lock-in, [D1](https://developers.cloudflare.com/d1/) is cheaper per-write at M-size and is a natural next step. If you're on AWS, on-prem, or want your data portable, managed Postgres is the typical destination. Either way — graduation is a Baerly win, not a churn event.
94
+
95
+ **Export to a database service** (swap `--target=` for `sqlite`, `postgres`, or `d1`):
181
96
 
182
97
  ```sh
183
98
  baerly export --target=postgres \
@@ -185,27 +100,14 @@ baerly export --target=postgres \
185
100
  --collection=<collection-name> --output=./out.sql
186
101
  ```
187
102
 
188
- The export is a **point-in-time** snapshot and honors any active
189
- schema on the collection. Your data was already in your bucket and
190
- your code is a portable HTTP server, so the graduation doesn't
191
- require vendor cooperation.
103
+ The export is a **point-in-time** snapshot and honors any active schema on the collection. Your data was already in your bucket and your code is a portable HTTP server, so the graduation doesn't require vendor cooperation.
192
104
 
193
105
  ## Production auth
194
106
 
195
- The scaffold ships `auth: "none"` so the day-1 happy path works
196
- with zero env vars; every request resolves to `config.tenant`.
197
- Before deploy, follow `AGENTS.md` → "Going to production":
198
-
199
- - **Pattern B — `auth: "shared-secret"`.** Single-tenant
200
- server-to-server callers (CI and internal services). Flip
201
- `auth` in `baerly.config.ts` and put `SHARED_SECRET` in
202
- `process.env` (your PaaS / secret manager).
203
- - **Pattern C — JWKS-backed JWT (recommended for multi-tenant).**
204
- Same artifact in dev and prod; the factory `verifier:` override
205
- engages when `JWKS_URL` is set. `bearerJwt()` (re-exported from
206
- `@gusto/baerly-storage/auth`) validates against your IdP's JWKS endpoint
207
- (`https://<issuer>/.well-known/jwks.json`) with `JWT_ISSUER` +
208
- `JWT_AUDIENCE` and pins the tenant from a claim.
107
+ The scaffold ships `auth: "none"` so the day-1 happy path works with zero env vars; every request resolves to `config.tenant`. Before deploy, follow `AGENTS.md` → "Going to production":
108
+
109
+ - **Pattern B — `auth: "shared-secret"`.** Single-tenant server-to-server callers (CI and internal services). Flip `auth` in `baerly.config.ts` and put `SHARED_SECRET` in `process.env` (your PaaS / secret manager).
110
+ - **Pattern C — JWKS-backed JWT (recommended for multi-tenant).** Same artifact in dev and prod; the factory `verifier:` override engages when `JWKS_URL` is set. `bearerJwt()` (re-exported from `@gusto/baerly-storage/auth`) validates against your IdP's JWKS endpoint (`https://<issuer>/.well-known/jwks.json`) with `JWT_ISSUER` + `JWT_AUDIENCE` and pins the tenant from a claim.
209
111
 
210
112
  ## Pointers
211
113
 
@@ -6,21 +6,23 @@
6
6
  "scripts": {
7
7
  "dev": "vite",
8
8
  "build": "tsc -b && vite build",
9
- "start": "node --experimental-strip-types src/server/index.ts",
9
+ "start": "node src/server/index.ts",
10
10
  "test": "vitest run",
11
11
  "typecheck": "tsc -b --noEmit",
12
12
  "verify": "pnpm run typecheck && pnpm run test"
13
13
  },
14
14
  "dependencies": {
15
- "@gusto/baerly-storage": "workspace:*",
16
- "aws4fetch": "1.0.20"
15
+ "@gusto/baerly-storage": "workspace:*"
17
16
  },
18
17
  "devDependencies": {
19
- "@types/node": "^26.0.1",
20
- "happy-dom": "^20.10.6",
21
- "typescript": "^6.0.3",
22
- "vite": "^8.1.2",
23
- "vitest": "^4.1.9"
18
+ "@types/node": "^26.6.6",
19
+ "happy-dom": "^21.0.4",
20
+ "typescript": "^7.0.2",
21
+ "vite": "^8.3.8",
22
+ "vitest": "^5.1.0"
24
23
  },
25
- "packageManager": "pnpm@11.1.2"
24
+ "engines": {
25
+ "node": ">=26"
26
+ },
27
+ "packageManager": "pnpm@12.22.0"
26
28
  }
@@ -1,9 +1,14 @@
1
- # pnpm 11 reads the postinstall-script allowlist only from this
2
- # file: `package.json#pnpm.*` is no longer honoured. Without this
3
- # map, `pnpm install` exits with `ERR_PNPM_IGNORED_BUILDS` for the
4
- # bundler chain below.
5
- #
6
- # `esbuild` ships a working install script we want to run (it
7
- # arrives via vite).
8
- allowBuilds:
9
- esbuild: true
1
+ # No `allowBuilds`: nothing in this dependency tree needs an install
2
+ # script (vite 8 only lists esbuild as an optional peer). pnpm fails the
3
+ # install on any unlisted package that gains one, so a new script is
4
+ # reviewed before it runs, not skipped silently.
5
+
6
+ # Supply-chain guardrails, strict by default — loosen one deliberately:
7
+ # - minimumReleaseAge: don't resolve a version until it has been on
8
+ # the registry a day, closing the publish-then-yank window.
9
+ # - trustPolicy: fail if a package's publishing trust (provenance,
10
+ # trusted publisher) drops below what earlier versions had.
11
+ # - blockExoticSubdeps: only direct deps may come from git or tarballs.
12
+ minimumReleaseAge: 1440
13
+ trustPolicy: no-downgrade
14
+ blockExoticSubdeps: true
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "compilerOptions": {
3
3
  "target": "ES2024",
4
- "lib": ["ES2024", "DOM", "DOM.Iterable"],
4
+ "lib": ["ES2024", "ESNext.TypedArrays", "ESNext.Collection", "DOM"],
5
5
  "module": "ESNext",
6
6
  "moduleResolution": "bundler",
7
7
  "allowImportingTsExtensions": true,
@@ -19,10 +19,9 @@
19
19
  "isolatedModules": true,
20
20
  "erasableSyntaxOnly": true,
21
21
 
22
- "esModuleInterop": true,
23
22
  "skipLibCheck": true,
24
23
  "types": ["vite/client"],
25
24
  "composite": true
26
25
  },
27
- "include": ["src/web/**/*", "uint8array-base64.d.ts", "types.ts", "baerly.config.ts"]
26
+ "include": ["src/web/**/*", "types.ts", "baerly.config.ts"]
28
27
  }
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "compilerOptions": {
3
3
  "target": "ES2024",
4
- "lib": ["ES2024", "DOM", "DOM.Iterable"],
4
+ "lib": ["ES2024", "ESNext.TypedArrays", "ESNext.Collection", "DOM"],
5
5
  "module": "ESNext",
6
6
  "moduleResolution": "bundler",
7
7
  "allowImportingTsExtensions": true,
@@ -19,10 +19,9 @@
19
19
  "isolatedModules": true,
20
20
  "erasableSyntaxOnly": true,
21
21
 
22
- "esModuleInterop": true,
23
22
  "skipLibCheck": true,
24
23
  "types": ["node"],
25
24
  "composite": true
26
25
  },
27
- "include": ["src/server/**/*", "uint8array-base64.d.ts", "types.ts", "baerly.config.ts"]
26
+ "include": ["src/server/**/*", "types.ts", "baerly.config.ts"]
28
27
  }