The branch merges thirteen shared library files, including two new modules, so every bundle that imports them was carrying older bytes than its source. Found by building each of the twenty-two bundles the freshness step names, one at a time: all twenty-two build cleanly in 8-24 seconds, none fails and none hangs -- and twenty of them produce different bytes. Big Picture alone moves 510 bytes. That also corrects a check I trusted earlier in this branch. `bun run tree` reported zero changed files and I read it as "the consumers are fresh". It is not: tree stages assets and regenerates leaf pages, and does NOT rebuild the bundles, so it can report a clean tree over twenty stale ones. Only a build answers that question. Hashes rebaked and check:sri passes across every leaf. |
||
|---|---|---|
| .. | ||
| dx-maps | ||
| README.md | ||
public/ — the built output
This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:
dx-maps/— the output folder: 25 plugin bundles and 37 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.dx-maps/index.html— the front page: the Plugin Studio, every plugin in one place.dx-maps/<plugin>/<plugin>.js— a plugin's bundle (a custom element; load it with a<script>tag).dx-maps/<plugin>/<page>/index.html— a ready-made page for one plugin view (embed it in an<iframe>).dx-maps/manifest.json— every plugin, page and embed snippet, machine-readable.dx-maps/assets/— the data, fonts and images the plugins fetch at runtime.
The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in
plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.