Since 2026-09-28 resolveMapProvider returns MapLibre for 'auto' whether or not a token is present; only an explicit provider selects Mapbox. Four comments still said "Mapbox when a token is available": useMapProvider.js's own header (and its note on the `token` argument), useMapInstance.js at the provider option, check-provider-switch.mjs's contract note, and the PROVIDER note that generate-tree writes into every leaf page. The leaf page's note now says what the page does: it finds a token first only when one is on offer, because place search uses one on either engine, and the element decides the engine. The 64 leaf pages are regenerated and differ only in that note. The three JS files change in comments only (compared minified, without renaming). |
||
|---|---|---|
| .. | ||
| 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.