Build-time work stays out of requests
The existing asset writer emits output identified by a hash of its content. The Worker reads that output through static assets.ΒΆ
The code-snippets design brief14 keeps Git reads and highlighting in build-time work. Request-time work receives static output. It does not resolve Git objects or start Shiki.ΒΆ
The proposed check verifies that neither the snippet package nor Shiki enters the startup bundle. The existing startup budget limits:ΒΆ
Check the modules included in the bundle, as well as its size, to verify which packages it includes.ΒΆ
Checks before writing output9 finish before assets are written. Pinned sources9 require no generation-time network fetch.ΒΆ
See the glossary for build-time work and request-time work.ΒΆ
Sources
- Asset emission. Primary source. Build output Accessed 2026-10-02.
- Static assets. Primary source. Request-time asset access Accessed 2026-10-02.
- Startup budget. Primary source. Worker bundle limits Accessed 2026-10-02.
Last changed 2026-10-10 in 978dccc. Source on GitHub. Change log.
Linked from
- Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
Build-time work stays out of requests β Git reads and highlighting produce static assets before the Worker handles requests.
- Change log. What changed in the files served here, newest first.
Build-time work stays out of requests β edited: docs: point live docs, skills and Brain pages at apps/site
- Code snippets quote a pinned source. Shipped design brief: pinned Git objects, typed diagnostics, and one build-only snippet model for both views.
Build-time work stays out of requests.
- Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
- Pin the source and report drift separately. A pinned excerpt stays fixed while a separate diagnostic compares it with HEAD.
This boundary keeps build-time work local.
- Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.
Build-time work stays out of requests β Git reads and highlighting produce static assets before the Worker handles requests.
- Source change history (log.md). The generated change log as Markdown.
Build-time work stays out of requests β edited: docs: point live docs, skills and Brain pages at apps/site
Unlinked mentions (1)
- Code snippets quote a pinned source β Content-addressed output and Turbo provide reuse between builds.ΒΆ