A TypeScript bundle is one file per entrypoint, bundled in the toolchain (hq ADR 0193); a toolchain follows the SDK it stands on (hq issue 212) #247

2026-10-03T21:26:28Z

mesh-admin commented

2026-10-03 21:26:28 +00:00

One-file bundles. Every served bundle is its own process (ADR 0193), so it carries its own copy of what it imports. After the compile and the launchers, the TypeScript toolchain's esbuild (Toolchain.Bundler, run as the native binary) bundles every entrypoint in place and every launcher under its own name (--out-extension:.js=.mjs) into one ES module file, --platform=node --target=node22, the SDK inlined, a createRequire banner so inlined CommonJS finds require, shebang kept, launchers 0755, a {"type":"module"} package.json beside them. The toolchain's node_modules is copied only when an artifact names external packages (new field, TypeScript bundles only). A toolchain image without the bundler is refused by name. Launchers keep their names, so the composer is unchanged; a process running node daemon/index.js runs the bundled file.

Measured on nftables in the toolchain image: 355,377 → 7,046 bytes gzipped, 235 → 3 files; the bundled launcher served node-packet-filter.rules/reload/remove and firewall_rules from a bare node:22 container with no node_modules.

Issue 212. No new mechanism needed: build.on already passes another module's artifact by its recorded reference, and a published package records @novox/mesh-sdk@0.1.6; it also already makes a plan edge. Tests now say both (TestAPackageTheMeshPublishedIsPassedByItsExactVersion, TestAToolchainStandingOnTheSDKFollowsIt). The mesh-tools side is mesh-tools #44.

Tests: bundling invocation and no node_modules copy; external packages; full suite passes against current catalogue and mesh-host.

Merge after mesh-tools #44 has built (toolchain with esbuild), then rebuild TypeScript bundles.

**One-file bundles.** Every served bundle is its own process (ADR 0193), so it carries its own copy of what it imports. After the compile and the launchers, the TypeScript toolchain's esbuild (`Toolchain.Bundler`, run as the native binary) bundles every entrypoint in place and every launcher under its own name (`--out-extension:.js=.mjs`) into one ES module file, `--platform=node --target=node22`, the SDK inlined, a `createRequire` banner so inlined CommonJS finds `require`, shebang kept, launchers 0755, a `{"type":"module"}` package.json beside them. The toolchain's node_modules is copied only when an artifact names `external` packages (new field, TypeScript bundles only). A toolchain image without the bundler is refused by name. Launchers keep their names, so the composer is unchanged; a `process` running `node daemon/index.js` runs the bundled file. Measured on nftables in the toolchain image: **355,377 → 7,046 bytes gzipped, 235 → 3 files**; the bundled launcher served `node-packet-filter.rules/reload/remove` and `firewall_rules` from a bare node:22 container with no node_modules. **Issue 212.** No new mechanism needed: `build.on` already passes another module's artifact by its recorded reference, and a published package records `@novox/mesh-sdk@0.1.6`; it also already makes a plan edge. Tests now say both (`TestAPackageTheMeshPublishedIsPassedByItsExactVersion`, `TestAToolchainStandingOnTheSDKFollowsIt`). The mesh-tools side is mesh-tools #44. Tests: bundling invocation and no node_modules copy; external packages; full suite passes against current catalogue and mesh-host. **Merge after mesh-tools #44 has built** (toolchain with esbuild), then rebuild TypeScript bundles.

mesh-admin added 2 commits 2026-10-03 21:26:29 +00:00

A TypeScript bundle is one file per entrypoint, bundled in the toolchain (hq ADR 0193); a toolchain follows the SDK it stands on (hq issue 212) ba189e6943

Every served bundle is its own process now, so each carries its own copy of what it imports: after
the compile and the launchers, the toolchain image's esbuild bundles every entrypoint in place and
every launcher under its own name into one ES module file, the SDK inlined, require provided to
inlined CommonJS, the launcher's shebang kept and its mode 0755. The toolchain's node_modules is
copied only for packages an artifact names external. An image without the bundler is refused by
name. Issue 212: build.on already passes a published package by its exact version and plans the
toolchain after it; tests say so.

Run the toolchain's esbuild as itself: npm installs its native binary in place of the script b0b3d87fe2

mesh-admin merged commit c0c3c3fed4 into main

2026-10-03 21:50:45 +00:00

mesh-admin deleted branch feat/a-typescript-bundle-is-one-file

2026-10-03 21:50:46 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#247