On a drop-in host's dev server a missing posters/<id>.webp answered 200 text/html (the app's own page), and export handed that page to the print dialog as the image. The .html source path had the same hole: the rasteriser lifts the first <svg> on whatever page it is given. library/packet/poster-fetch.js now fetches both. A raster counts only if it is an image: by content-type, or by its first bytes when a host labels a WebP application/octet-stream. A source counts only if it is a poster document (its class="stage" element); a 200 that is not one reports 404. A thrown fetch on the raster stays a miss, so the source fallback still runs; a thrown fetch on the source is still reported as itself. Measured against a real local HTTP server with a single-page-app fallback: real WebP accepted (image/webp and octet-stream), missing WebP refused (200 fallback page and 404), real source accepted, missing source 404 (200 fallback page and 404), unreachable host a miss for the raster and "fetch failed" for the source. usePosterPrints uses it. PosterWall follows in its own commit. |
||
|---|---|---|
| .. | ||
| api | ||
| charts/whiteboard | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| dashboards | ||
| data | ||
| elements | ||
| i18n | ||
| layouts | ||
| lists | ||
| maps | ||
| packet | ||
| packets | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| vendor/cldr | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.