clay / claycli / 25932771886 / 1

87%

master: 87%

Pull #250

github

🍕 Clarify _client-init.js component-mounting semantics in docs

Several places in CLAY-VITE.md and BUNDLER-COMPARISON.md described the
legacy Browserify component loader as "mounts every .client module
loaded — no DOM check" or "DOM or not". That overstates what
_client-init.js actually does.

Per lib/cmd/compile/_client-init.js, mountComponentModules() iterates
every .client key in window.modules and calls window.require(key) on
each — which executes the module body and walks its dependency graph
regardless of DOM presence — but the exported controller function is
only invoked via tryToMount() for elements matching the
[data-uri*="_components/<name>/"] / [data-uri$="_components<name>"]
selectors. So the mount call itself IS DOM-gated; what isn't gated is
module evaluation.

The Vite improvement is therefore narrower but still real: vite-bootstrap
scans the DOM first and skips the dynamic import() entirely if no
matching element exists, so neither the module body nor any of its
transitive dependencies execute. Updated all four prose locations to
reflect this; the mermaid diagrams already used the more precise
"calls window.require(key) for every .client / regardless of DOM
presence" wording and were left as-is.

Co-authored-by: Cursor <cursoragent@cursor.com>

757 of 941 branches covered (80.45%)

Branch coverage included in aggregate %.

1581 of 1751 relevant lines covered (90.29%)

10.28 hits per line