8124708d12
Some checks are pending
build-gate / build (push) Waiting to run
THE DEV SERVER LANDED ON THE WRONG PAGE. `bun run dev` served only the staging gallery at /, and had no route for a bundle leaf, so there was no URL at which the capability-5 plugin studio could be seen at all. Opening / showed plugins wrapped in per-bundle frames behind a wall of explanatory prose, which reads as "none of the elements are working" when in fact the elements were fine and the page was a chooser. / now mounts <plugin-studio> directly: a 605-byte host page with no chrome and no prose, the element filling the viewport, and the Mapbox token baked as the token ladder's first rung so maps work without anyone appending ?tk=. The gallery is not deleted — it still generates the built index and is load-bearing for the manifest — it simply moves to an explicit /__gallery URL and stops being the landing surface. tree-base is passed explicitly, without which the studio mounts EMPTY. It builds its tab list by fetching <base>manifest.json and falls back to a path relative to its own script URL, which in dev resolves to a file that does not exist. The dev server serves the same manifest-shaped model on its own route, so dev now shows the same tab list as production: 19 bundles, 30 profiles, five capability groups. PLUGIN FRAMES SHOWED THE GALLERY. The studio nests map profiles in a lazy iframe pointed at that profile's leaf page, and dev had no such page, so each frame fell through to the SPA fallback and rendered / — the gallery, recursively, once per map tab. A /__leaf/<bundle>/<profile> route now serves the dev equivalent of the built tree's leaf: one element, its bundle entry, the token, and nothing else. |
||
|---|---|---|
| .. | ||
| dev-plugin.mjs | ||
| discover.mjs | ||