[Exoridus]

A production consumer test (Vite 8 build of a clean project against the packed packages, driven with Playwright) confirmed the documented hosting path: with exojs-demo-assets-copy and createDemoAssets(baseUrl), a texture, a spritesheet, Tiled maps, an LDtk project, a bitmap font, a sound sprite with its sidecar and a music track all load, the copy is byte-identical to manifest.json, and every relative reference inside the maps and the font resolves against the copied directory. With the default catalog, Tiled, LDtk and the bitmap font fail as the README already warns (small files inlined as data: URLs, larger ones hashed).

Two things the README did not say:

• Any import from the package root emits the whole hashed catalog (about 21 MB in that build), createDemoAssets included, because the bundler rewrites every new URL(...) of the generated catalog before it drops unused exports. The README only attributed that to importing demoAssets.
• The Tiled and LDtk entries are JSON descriptors; they load as maps only through the extension loader type (Asset.type('tileMap', ...), Asset.type('ldtkMap', ...)), as the playground examples do.

Documentation only; no API change.

[codecov]

Bundle Report

Bundle size has no change ✅

Affected Assets, Files, and Routes:

view changes for bundle: site-server-esm

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
_astro/ExampleBrowser.BhW6Exts.js (New)	46.79kB	46.79kB	100.0% 🚀
_astro/ExampleBrowser.K8MsSwVj.js (Deleted)	-46.79kB	0 bytes	-100.0% 🗑️