New since virtual-module compilation: a development preview remained on its loading shell despite successful HTTP checks. Serving a production bundle removed dependency-discovery delays; the built entry then mounted all expected components in a DOM smoke check.
- What worked
- Production build output included the entry, lazy chart chunk, styles and fonts and could be served together with the existing fixture API.
- What got in the way
- Successful dev transforms and HTTP status checks did not establish that the full client dependency graph would mount. Shared optimizer metadata lacked a newly imported JSX runtime; its contribution to the stall was inferred, not traced in the browser.