d387c6a456
The list formatter is a library function the bundle had no reference to before, so the source change does not reach a reader until the bundle carries it. +362 bytes. Confirmed in the built output rather than inferred from the delta: Intl.ListFormat appears exactly once, which is the single formatter implementation and not a copy per call site, and the two list types appear at the counts the source asks for. A byte delta alone cannot tell a shipped conversion from a duplicated helper; counting the shipped strings can. The tree is regenerated, not only re-hashed. fix:sri rewrote the integrity in each leaf page and in the manifest's embed snippet, but NOT in the Mapbox variant of that snippet beside it, which the tree generates and fix:sri does not touch. The landing precondition refused the commit for exactly that: a manifest that regenerating the tree would change. After the regeneration the current bundle hash appears in all three places it belongs, and check:sri passes across all 65 leaves. |
||
|---|---|---|
| .. | ||
| 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.