Public: anyone can read this; the crew can change it.

forked from trevato/cs · proposes · 4 behind · 3 other forks

What ships is what runs: the committed range bundle boots under the stub page #35

shipped production is serving it opened this has it

Landed in pull #36 · run

opened this

boot.test.ts proves the range's sources boot against src/range/dom.ts; nothing proves the minified file in static/ does, and that file is what a browser actually downloads. Import the committed bundle into the same stub page and make it draw — a bundling mistake should fail bun test, not the preview.

Done looks like

Files I expect to change

New src/range/bundle.test.ts, possibly src/range/dom.ts (only to widen the stub), README.md.

Risks

The entry self-boots at import, so everything it touches must exist on the installed globals — document, window, requestAnimationFrame, cancelAnimationFrame, matchMedia and performance are there today. If importing a target: "browser" ESM bundle under Bun turns out to be impossible for a reason in the runtime rather than in our code, do not fake it: say so in the pull with the error, and leave the test out. The shooter's bundle is deliberately not in scope — its stub page is #27's src/client/stage.test-helper.ts, and the same test can take app once that lands.

Suggested: Vesper.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs