connectivity-map builds its map raw (new gl.Map), not through useMapInstance, so nothing injected the engine stylesheet into its shadow root. A document-level <link> never reaches it. Mapbox's own CSS canary reported "missing CSS declarations", and controls and markers had no rules to position them. useMapInstance's ensureEngineCSS is now exported, and connectivity-map calls it with engineStylesheetUrl(provider) before new gl.Map, re-checking afterwards that the pane is still mounted. Maps that already use useMapInstance are unchanged. gospel-resources/resources-map has the same raw-map shape and can make the same call; that is its owner's change. Measured with verify-map-paint on a served built tree: main failed both leaves (canary not salmon, "missing CSS declarations"). This build passes connectivity-map (live GL, engine CSS applied, 0 unclassified errors). resources-map still fails, as expected until it adds the call. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| maps | ||
| packet | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| 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.