From 871600e7f7b74481a4939d2e5b36bcde6e975e7b Mon Sep 17 00:00:00 2001 From: Doug Mealing Date: Thu, 12 Nov 2026 22:54:11 -0500 Subject: [PATCH 1/4] fix(codegen-ts-*): drop the @biomejs/biome peer so the CLI stops installing the native binary codegen-ts-react, codegen-ts-tanstack and codegen-ts-angular declared @biomejs/biome as a peer, which npm auto-installs, putting the ~94 MB native @biomejs/cli- binary into every CLI install. Nothing shipped uses it: formatting goes through @biomejs/wasm-nodejs. The devDependency stays for the repo's lint gate. check-peer-ranges.ts now rejects a publishable package that requires the native formatter. Fresh CLI install: 245 MB -> 151 MB. --- CHANGELOG.md | 8 ++++ bun.lock | 9 ----- scripts/check-peer-ranges.ts | 38 ++++++++++++++++++- scripts/check-reference-templates-lint.ts | 5 ++- .../packages/codegen-ts-angular/package.json | 3 -- .../packages/codegen-ts-react/package.json | 3 -- .../packages/codegen-ts-tanstack/package.json | 3 -- 7 files changed, 48 insertions(+), 21 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3aa9f96685..cc8c82846b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -41,6 +41,14 @@ loaded before stops loading. This vocabulary ships in 1.3.0 with `metamodelVersi and the `metaobjects-authoring` skill now send grouped totals, dashboard numbers and read-only report views to `object.report` (`references/declaring-reports.md`) before the `@sql` escape, which they describe as the last resort for bodies the vocabulary cannot express. +- **`@metaobjectsdev/cli` no longer installs the native Biome binary.** `codegen-ts-react`, + `codegen-ts-tanstack` and the source-only `codegen-ts-angular` declared `@biomejs/biome` as a + peer dependency, which npm installs automatically, so every CLI install carried the ~94 MB + `@biomejs/cli-` binary that nothing runs: codegen formats through the WebAssembly + build (`@biomejs/wasm-nodejs`). The peer is gone (it stays a devDependency for this repo's own + lint gate), and a fresh npm install of the CLI drops from 245 MB to 151 MB of `node_modules`. + `scripts/check-peer-ranges.ts` now fails a publishable package that requires `@biomejs/biome` + through `dependencies` or a non-optional peer. ### Fixed diff --git a/bun.lock b/bun.lock index f0968a3712..5f8e86e3c9 100644 --- a/bun.lock +++ b/bun.lock @@ -221,9 +221,6 @@ "bun-types": "latest", "typescript": "^5.6.0", }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0", - }, }, "server/typescript/packages/codegen-ts-react": { "name": "@metaobjectsdev/codegen-ts-react", @@ -239,9 +236,6 @@ "bun-types": "latest", "typescript": "^5.6.0", }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0", - }, }, "server/typescript/packages/codegen-ts-tanstack": { "name": "@metaobjectsdev/codegen-ts-tanstack", @@ -257,9 +251,6 @@ "bun-types": "latest", "typescript": "^5.6.0", }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0", - }, }, "server/typescript/packages/conformance": { "name": "@metaobjectsdev/conformance", diff --git a/scripts/check-peer-ranges.ts b/scripts/check-peer-ranges.ts index 2884ff3652..5033d3f29d 100755 --- a/scripts/check-peer-ranges.ts +++ b/scripts/check-peer-ranges.ts @@ -25,6 +25,15 @@ * version we chose — never the version an adopter would get. This check works because * it reads MANIFESTS, not `node_modules`, so it needs no network and cannot be fooled * by a warm lockfile. + * + * Second rule, same walk: no publishable package may REQUIRE the native Biome + * formatter (`@biomejs/biome`, which pulls a ~94 MB per-platform `@biomejs/cli-*` + * binary) through `dependencies` or a non-optional peer. npm installs required peers + * automatically, so a single generator package declaring it put the binary into every + * `@metaobjectsdev/cli` install, though nothing at run time uses it: codegen formats + * through the WebAssembly build (`@biomejs/wasm-nodejs` + `@biomejs/js-api`, see + * `codegen-ts/src/format.ts`). Development use belongs in `devDependencies`; a genuine + * run-time need must be an optional peer (`peerDependenciesMeta`). */ import { readdirSync, readFileSync, existsSync } from "node:fs"; import { join } from "node:path"; @@ -35,8 +44,13 @@ const ROOTS = ["server/typescript/packages", "client/web/packages"]; /** A version no real release will reach. If the range still matches, it has no ceiling. */ const BEYOND_ANY_REAL_VERSION = "9999.0.0"; +/** The native formatter and its per-platform binaries. */ +const isNativeFormatter = (name: string): boolean => + name === "@biomejs/biome" || name.startsWith("@biomejs/cli-"); + interface Violation { pkg: string; peer: string; range: string } const violations: Violation[] = []; +const nativeFormatter: { pkg: string; dep: string; field: string }[] = []; let checked = 0; for (const root of ROOTS) { @@ -44,9 +58,20 @@ for (const root of ROOTS) { const manifest = join(REPO, root, dir, "package.json"); if (!existsSync(manifest)) continue; const pkg = JSON.parse(readFileSync(manifest, "utf8")) as { - name: string; private?: boolean; peerDependencies?: Record; + name: string; private?: boolean; + dependencies?: Record; + peerDependencies?: Record; + peerDependenciesMeta?: Record; }; if (pkg.private === true) continue; // never published — its peers bind nobody + for (const dep of Object.keys(pkg.dependencies ?? {})) { + if (isNativeFormatter(dep)) nativeFormatter.push({ pkg: pkg.name, dep, field: "dependencies" }); + } + for (const dep of Object.keys(pkg.peerDependencies ?? {})) { + if (isNativeFormatter(dep) && pkg.peerDependenciesMeta?.[dep]?.optional !== true) { + nativeFormatter.push({ pkg: pkg.name, dep, field: "peerDependencies (required)" }); + } + } for (const [peer, range] of Object.entries(pkg.peerDependencies ?? {})) { checked++; if (Bun.semver.satisfies(BEYOND_ANY_REAL_VERSION, range)) { @@ -71,4 +96,15 @@ if (violations.length > 0) { process.exit(1); } +if (nativeFormatter.length > 0) { + console.error("✖ native Biome formatter required at install time:\n"); + for (const v of nativeFormatter) console.error(` ${v.pkg}\n ${v.field}: "${v.dep}"`); + console.error( + `\nnpm installs it (a ~94 MB native binary) into every adopter's tree, and codegen` + + `\nformats through @biomejs/wasm-nodejs instead. Move it to devDependencies, or, if` + + `\nshipped code really needs it, mark the peer optional in peerDependenciesMeta.\n`, + ); + process.exit(1); +} + console.log(`peer-range bounds: OK (${checked} peer ranges, all bounded)`); diff --git a/scripts/check-reference-templates-lint.ts b/scripts/check-reference-templates-lint.ts index aaec9441a6..9602ca7da0 100644 --- a/scripts/check-reference-templates-lint.ts +++ b/scripts/check-reference-templates-lint.ts @@ -76,8 +76,9 @@ export async function discoverTemplates(repo: string = REPO): Promise return found.sort(); } -/** biome is a dependency of the codegen packages (it runs the `formatTs` pass), so a - * binary is present after `bun install`. Any of them is the same pinned version. */ +/** biome is a devDependency of the codegen packages (shipped code formats through the + * WASM build instead), so a binary is present after `bun install`. Any of them is the + * same pinned version. */ export function resolveBiomeBin(repo: string = REPO): string | undefined { for (const root of PACKAGE_ROOTS) { const rootDir = join(repo, root); diff --git a/server/typescript/packages/codegen-ts-angular/package.json b/server/typescript/packages/codegen-ts-angular/package.json index 58c65363f7..1d456ab319 100644 --- a/server/typescript/packages/codegen-ts-angular/package.json +++ b/server/typescript/packages/codegen-ts-angular/package.json @@ -50,9 +50,6 @@ "@metaobjectsdev/codegen-ts": "workspace:*", "ts-poet": "^6.10.0" }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0" - }, "devDependencies": { "@biomejs/biome": "^1.9.0", "bun-types": "latest", diff --git a/server/typescript/packages/codegen-ts-react/package.json b/server/typescript/packages/codegen-ts-react/package.json index 26045c8911..57ab1b9b44 100644 --- a/server/typescript/packages/codegen-ts-react/package.json +++ b/server/typescript/packages/codegen-ts-react/package.json @@ -49,9 +49,6 @@ "@metaobjectsdev/codegen-ts": "workspace:*", "ts-poet": "^6.10.0" }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0" - }, "devDependencies": { "@biomejs/biome": "^1.9.0", "@metaobjectsdev/test-generators": "workspace:*", diff --git a/server/typescript/packages/codegen-ts-tanstack/package.json b/server/typescript/packages/codegen-ts-tanstack/package.json index d5f890d14e..6b6a795934 100644 --- a/server/typescript/packages/codegen-ts-tanstack/package.json +++ b/server/typescript/packages/codegen-ts-tanstack/package.json @@ -48,9 +48,6 @@ "@metaobjectsdev/codegen-ts": "workspace:*", "ts-poet": "^6.10.0" }, - "peerDependencies": { - "@biomejs/biome": ">=1.9.0 <3.0.0" - }, "devDependencies": { "@biomejs/biome": "^1.9.0", "@metaobjectsdev/test-generators": "workspace:*", From c27faecc3a1edddc64085d3acee53c87d64ff267 Mon Sep 17 00:00:00 2001 From: Doug Mealing Date: Thu, 12 Nov 2026 23:00:00 -0500 Subject: [PATCH 2/4] fix(cli): make the libSQL driver an optional peer so a Postgres-only install skips it @libsql/kysely-libsql was a direct dependency of @metaobjectsdev/cli, so every install carried it and its native addon. The CLI already imports it lazily, only for a sqlite URL on Node, and prints a package-manager-specific install command when it is missing. It is now an optional peer bounded like migrate-ts's, kept as a devDependency for the CLI's own tests. Fresh CLI install with the Biome change: 245 MB -> 101 MB. --- CHANGELOG.md | 13 ++++++++++--- bun.lock | 4 +++- server/typescript/packages/cli/README.md | 5 +++-- server/typescript/packages/cli/package.json | 6 +++++- 4 files changed, 21 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index cc8c82846b..1ff9b82149 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -46,9 +46,16 @@ loaded before stops loading. This vocabulary ships in 1.3.0 with `metamodelVersi peer dependency, which npm installs automatically, so every CLI install carried the ~94 MB `@biomejs/cli-` binary that nothing runs: codegen formats through the WebAssembly build (`@biomejs/wasm-nodejs`). The peer is gone (it stays a devDependency for this repo's own - lint gate), and a fresh npm install of the CLI drops from 245 MB to 151 MB of `node_modules`. - `scripts/check-peer-ranges.ts` now fails a publishable package that requires `@biomejs/biome` - through `dependencies` or a non-optional peer. + lint gate). `scripts/check-peer-ranges.ts` now fails a publishable package that requires + `@biomejs/biome` through `dependencies` or a non-optional peer. +- **The libSQL driver is an optional peer of `@metaobjectsdev/cli`, like `pg`.** + `@libsql/kysely-libsql` was a direct dependency, so a Postgres-only install carried it and + its native addon. The CLI already loads it lazily and only for a `sqlite` URL on Node, and a + missing driver prints the install command for your package manager. **Upgrading:** a + project that runs `meta migrate`, `meta verify --db` or `meta verify --replay` against + SQLite on Node installs it (`npm install -D @libsql/kysely-libsql`); under Bun, `migrate` + and `verify --db` use `bun:sqlite` and need nothing. Together with the Biome change, a fresh + npm install of the CLI drops from 245 MB to 101 MB of `node_modules`. ### Fixed diff --git a/bun.lock b/bun.lock index 5f8e86e3c9..2801fc6a35 100644 --- a/bun.lock +++ b/bun.lock @@ -141,7 +141,6 @@ "dependencies": { "@biomejs/js-api": "^0.7.0", "@biomejs/wasm-nodejs": "^1.9.4", - "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/codegen-ts": "workspace:*", "@metaobjectsdev/codegen-ts-react": "workspace:*", "@metaobjectsdev/codegen-ts-tanstack": "workspace:*", @@ -156,6 +155,7 @@ }, "devDependencies": { "@libsql/client": "^0.14.0", + "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/test-generators": "workspace:*", "@types/node": "^22.0.0", "@types/pg": "^8.0.0", @@ -170,10 +170,12 @@ "zod": "^4.4.3", }, "peerDependencies": { + "@libsql/kysely-libsql": ">=0.4.0 <0.5.0", "kysely": ">=0.27.0 <0.30.0", "pg": ">=8.0.0 <9.0.0", }, "optionalPeers": [ + "@libsql/kysely-libsql", "pg", ], }, diff --git a/server/typescript/packages/cli/README.md b/server/typescript/packages/cli/README.md index 09477f99af..47aceceffb 100644 --- a/server/typescript/packages/cli/README.md +++ b/server/typescript/packages/cli/README.md @@ -12,8 +12,9 @@ The MetaObjects CLI — scaffolds `metaobjects/` + `.metaobjects/`, runs codegen bun add -D @metaobjectsdev/cli ``` -The SQLite/Turso driver (`@libsql/kysely-libsql`) ships as a direct dependency — `meta migrate` against a `sqlite`/`libsql` URL works out of the box. Postgres remains an optional peer (install only if you target Postgres): +Database drivers are optional peers, so an install carries only the one your dialect needs: - Postgres: `bun add -D pg` +- SQLite/Turso on Node (`meta migrate`, `meta verify --db`/`--replay` against a `file:`/`libsql:` URL): `bun add -D @libsql/kysely-libsql`. Under Bun the CLI uses the built-in `bun:sqlite` instead and needs no driver for `migrate` or `verify --db`. If a required driver is ever missing, the CLI prints an install command matching your project's package manager (npm / pnpm / yarn / bun, detected from the lockfile). @@ -44,7 +45,7 @@ bun build ./bin/meta.ts --compile --target=bun-windows-x64 --outfile dist/meta-w ### SQLite driver inside the binary -The standalone binary uses Bun's built-in **`bun:sqlite`** for the `sqlite` dialect (it ships inside the embedded Bun runtime). The npm/Node distribution uses the bundled `@libsql/kysely-libsql` dependency. This is automatic — the same `--db file:./app.db --dialect sqlite` flags work in both. (Postgres in the standalone binary still requires the `pg` peer to be resolvable, because `pg` is a native module that `--compile` cannot embed; sqlite is the fully self-contained path.) +The standalone binary uses Bun's built-in **`bun:sqlite`** for the `sqlite` dialect (it ships inside the embedded Bun runtime). The npm/Node distribution uses the optional `@libsql/kysely-libsql` peer, which you install when you target SQLite. This is automatic — the same `--db file:./app.db --dialect sqlite` flags work in both. (Postgres in the standalone binary still requires the `pg` peer to be resolvable, because `pg` is a native module that `--compile` cannot embed; sqlite is the fully self-contained path.) Run schema ops from the compiled binary: diff --git a/server/typescript/packages/cli/package.json b/server/typescript/packages/cli/package.json index bfeb8bcc5e..d86f3c9e3b 100644 --- a/server/typescript/packages/cli/package.json +++ b/server/typescript/packages/cli/package.json @@ -50,7 +50,6 @@ "dependencies": { "@biomejs/js-api": "^0.7.0", "@biomejs/wasm-nodejs": "^1.9.4", - "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/codegen-ts": "workspace:*", "@metaobjectsdev/codegen-ts-react": "workspace:*", "@metaobjectsdev/codegen-ts-tanstack": "workspace:*", @@ -64,16 +63,21 @@ "jiti": "^2.4.0" }, "peerDependencies": { + "@libsql/kysely-libsql": ">=0.4.0 <0.5.0", "kysely": ">=0.27.0 <0.30.0", "pg": ">=8.0.0 <9.0.0" }, "peerDependenciesMeta": { + "@libsql/kysely-libsql": { + "optional": true + }, "pg": { "optional": true } }, "devDependencies": { "@libsql/client": "^0.14.0", + "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/test-generators": "workspace:*", "@types/node": "^22.0.0", "@types/pg": "^8.0.0", From 7237f404170bcb9e50f9c6cd389a2158e6e99815 Mon Sep 17 00:00:00 2001 From: Doug Mealing Date: Thu, 12 Nov 2026 23:07:16 -0500 Subject: [PATCH 3/4] no-mistakes(review): Revert libSQL optional-peer change; keep Biome removal --- CHANGELOG.md | 13 +++---------- bun.lock | 4 +--- server/typescript/packages/cli/README.md | 5 ++--- server/typescript/packages/cli/package.json | 6 +----- 4 files changed, 7 insertions(+), 21 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1ff9b82149..cc8c82846b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -46,16 +46,9 @@ loaded before stops loading. This vocabulary ships in 1.3.0 with `metamodelVersi peer dependency, which npm installs automatically, so every CLI install carried the ~94 MB `@biomejs/cli-` binary that nothing runs: codegen formats through the WebAssembly build (`@biomejs/wasm-nodejs`). The peer is gone (it stays a devDependency for this repo's own - lint gate). `scripts/check-peer-ranges.ts` now fails a publishable package that requires - `@biomejs/biome` through `dependencies` or a non-optional peer. -- **The libSQL driver is an optional peer of `@metaobjectsdev/cli`, like `pg`.** - `@libsql/kysely-libsql` was a direct dependency, so a Postgres-only install carried it and - its native addon. The CLI already loads it lazily and only for a `sqlite` URL on Node, and a - missing driver prints the install command for your package manager. **Upgrading:** a - project that runs `meta migrate`, `meta verify --db` or `meta verify --replay` against - SQLite on Node installs it (`npm install -D @libsql/kysely-libsql`); under Bun, `migrate` - and `verify --db` use `bun:sqlite` and need nothing. Together with the Biome change, a fresh - npm install of the CLI drops from 245 MB to 101 MB of `node_modules`. + lint gate), and a fresh npm install of the CLI drops from 245 MB to 151 MB of `node_modules`. + `scripts/check-peer-ranges.ts` now fails a publishable package that requires `@biomejs/biome` + through `dependencies` or a non-optional peer. ### Fixed diff --git a/bun.lock b/bun.lock index 2801fc6a35..5f8e86e3c9 100644 --- a/bun.lock +++ b/bun.lock @@ -141,6 +141,7 @@ "dependencies": { "@biomejs/js-api": "^0.7.0", "@biomejs/wasm-nodejs": "^1.9.4", + "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/codegen-ts": "workspace:*", "@metaobjectsdev/codegen-ts-react": "workspace:*", "@metaobjectsdev/codegen-ts-tanstack": "workspace:*", @@ -155,7 +156,6 @@ }, "devDependencies": { "@libsql/client": "^0.14.0", - "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/test-generators": "workspace:*", "@types/node": "^22.0.0", "@types/pg": "^8.0.0", @@ -170,12 +170,10 @@ "zod": "^4.4.3", }, "peerDependencies": { - "@libsql/kysely-libsql": ">=0.4.0 <0.5.0", "kysely": ">=0.27.0 <0.30.0", "pg": ">=8.0.0 <9.0.0", }, "optionalPeers": [ - "@libsql/kysely-libsql", "pg", ], }, diff --git a/server/typescript/packages/cli/README.md b/server/typescript/packages/cli/README.md index 47aceceffb..09477f99af 100644 --- a/server/typescript/packages/cli/README.md +++ b/server/typescript/packages/cli/README.md @@ -12,9 +12,8 @@ The MetaObjects CLI — scaffolds `metaobjects/` + `.metaobjects/`, runs codegen bun add -D @metaobjectsdev/cli ``` -Database drivers are optional peers, so an install carries only the one your dialect needs: +The SQLite/Turso driver (`@libsql/kysely-libsql`) ships as a direct dependency — `meta migrate` against a `sqlite`/`libsql` URL works out of the box. Postgres remains an optional peer (install only if you target Postgres): - Postgres: `bun add -D pg` -- SQLite/Turso on Node (`meta migrate`, `meta verify --db`/`--replay` against a `file:`/`libsql:` URL): `bun add -D @libsql/kysely-libsql`. Under Bun the CLI uses the built-in `bun:sqlite` instead and needs no driver for `migrate` or `verify --db`. If a required driver is ever missing, the CLI prints an install command matching your project's package manager (npm / pnpm / yarn / bun, detected from the lockfile). @@ -45,7 +44,7 @@ bun build ./bin/meta.ts --compile --target=bun-windows-x64 --outfile dist/meta-w ### SQLite driver inside the binary -The standalone binary uses Bun's built-in **`bun:sqlite`** for the `sqlite` dialect (it ships inside the embedded Bun runtime). The npm/Node distribution uses the optional `@libsql/kysely-libsql` peer, which you install when you target SQLite. This is automatic — the same `--db file:./app.db --dialect sqlite` flags work in both. (Postgres in the standalone binary still requires the `pg` peer to be resolvable, because `pg` is a native module that `--compile` cannot embed; sqlite is the fully self-contained path.) +The standalone binary uses Bun's built-in **`bun:sqlite`** for the `sqlite` dialect (it ships inside the embedded Bun runtime). The npm/Node distribution uses the bundled `@libsql/kysely-libsql` dependency. This is automatic — the same `--db file:./app.db --dialect sqlite` flags work in both. (Postgres in the standalone binary still requires the `pg` peer to be resolvable, because `pg` is a native module that `--compile` cannot embed; sqlite is the fully self-contained path.) Run schema ops from the compiled binary: diff --git a/server/typescript/packages/cli/package.json b/server/typescript/packages/cli/package.json index d86f3c9e3b..bfeb8bcc5e 100644 --- a/server/typescript/packages/cli/package.json +++ b/server/typescript/packages/cli/package.json @@ -50,6 +50,7 @@ "dependencies": { "@biomejs/js-api": "^0.7.0", "@biomejs/wasm-nodejs": "^1.9.4", + "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/codegen-ts": "workspace:*", "@metaobjectsdev/codegen-ts-react": "workspace:*", "@metaobjectsdev/codegen-ts-tanstack": "workspace:*", @@ -63,21 +64,16 @@ "jiti": "^2.4.0" }, "peerDependencies": { - "@libsql/kysely-libsql": ">=0.4.0 <0.5.0", "kysely": ">=0.27.0 <0.30.0", "pg": ">=8.0.0 <9.0.0" }, "peerDependenciesMeta": { - "@libsql/kysely-libsql": { - "optional": true - }, "pg": { "optional": true } }, "devDependencies": { "@libsql/client": "^0.14.0", - "@libsql/kysely-libsql": "^0.4.0", "@metaobjectsdev/test-generators": "workspace:*", "@types/node": "^22.0.0", "@types/pg": "^8.0.0", From 0d578caefbf47f17d76a3edb3e7ad56eaedbeae6 Mon Sep 17 00:00:00 2001 From: Doug Mealing Date: Thu, 12 Nov 2026 23:28:36 -0500 Subject: [PATCH 4/4] no-mistakes(document): Fix CLI README Biome backend claim --- server/typescript/packages/cli/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/typescript/packages/cli/README.md b/server/typescript/packages/cli/README.md index 09477f99af..e5f43d0924 100644 --- a/server/typescript/packages/cli/README.md +++ b/server/typescript/packages/cli/README.md @@ -28,7 +28,7 @@ bun run build:binary # → dist/meta (compiled for the build host's OS/ar ./dist/meta --help ``` -The build externalizes two optional Biome WASM backends (`@biomejs/wasm-bundler`, `@biomejs/wasm-web`) that the CLI never loads — only the native Biome backend is used. +The build externalizes two optional Biome WASM backends (`@biomejs/wasm-bundler`, `@biomejs/wasm-web`) that the CLI never loads — codegen formats through the Node WebAssembly backend (`@biomejs/wasm-nodejs`), and the native Biome binary is not installed with the CLI. ### Cross-compiling for other platforms