build: guard the initial chunks by module id; main-chunk check in CI

Review of Task 0:
- build/initialChunkGuard.js, a Rollup plugin in the browser build, fails
  the build when an initial chunk (an entry and what it imports
  statically) holds a module from node_modules/three, @navaramap/* or
  postprocessing. Checked by forcing it on satellite.js, which the main
  chunk does hold: the build fails naming the chunk and module.
  navaraAssets.test now pins both build plugins.
- scripts/check-main-chunk.mjs is one script for both main-chunk checks:
  the composition (text markers in the initial chunks, sizes) and, when
  scripts/main-chunk-baseline.json exists, the phase-4 branch's gzip-9
  budget, with its exports (checkMainChunk, measureMainChunk) so the two
  branches merge into this file. The composition test moved to
  src/tooling/mainChunkComposition.test.mjs to leave phase 4's
  mainChunk.test.mjs its name.
- CI runs npm run check:main-chunk after each npm run build (unit,
  browser-gate and Windows jobs).
This commit is contained in:
German Khokhlov committed 2026-10-16 16:22:49 +04:00
1 parent f7f4e9a45c
commit 76851ee949
8 files changed
+289 -66

No files matched your search

+2 -2
View File
@@ -46,11 +46,11 @@ test('a build without Navara gets no Navara wasm', (t) => {
assert.deepEqual(emitted, []);
});
test('the browser build runs the Navara asset copy as a Rollup plugin', () => {
test('the browser build runs the Navara asset copy and the initial-chunk guard as Rollup plugins', () => {
const { build } = createBrowserViteConfig({});
assert.deepEqual(
build.rollupOptions.plugins.map(({ name }) => name),
['navara-worker-assets'],
['navara-worker-assets', 'gev-initial-chunk-guard'],
);
assert.equal(build.chunkSizeWarningLimit, 1500);
});