docs: maplibre v6 migration research#1
Open
garyo wants to merge 1 commit into
Open
Conversation
Adds docs/maplibre-v6-migration.md — full impact analysis of upgrading from maplibre-gl 5.24.0 to 6.x, covering all pre-release breaking changes, codebase touch points with file:line references, and a suggested upgrade order. https://claude.ai/code/session_01DLvs7r6qNfKdqmuzQF4EKr
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
pelorus-nav | 1d13051 | Commit Preview URL Branch Preview URL |
May 03 2026, 01:06 AM |
garyo
added a commit
that referenced
this pull request
Jul 10, 2026
The root URL is now a static marketing page (public/landing.html — sail-dart branding, live chart screenshots, feature overview, email signup); the app lives at /app. Groundwork for the pre-launch email list (planning doc 08: "the #1 asset"). - worker.ts rewrites "/" to the landing page and adds POST /api/subscribe (honeypot + validation, stored in the SUBSCRIBERS KV namespace keyed by lowercased email so repeats are idempotent) - wrangler.toml: run_worker_first for "/" and /api/* — asset matches otherwise bypass the worker entirely; new KV binding - PWA: start_url /app; SW navigation denylist for /, /landing.html, /api/*; landing assets excluded from the app precache - Vite dev server still serves the app at / (worker not involved); the landing page is previewable at /landing.html - Capacitor/native builds unaffected Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Research doc covering the impact of upgrading from
maplibre-gl@5.24.0to v6.x (currently at pre-release6.0.0-6; stable has not shipped yet).Risk level: Medium — no show-stoppers. Key findings:
GeoJSONSource.setDatasecond param removed (6.0.0-3): Zero exposure — none of our 35+ call sites pass a second argument.{get,set}PaintProperty/{get,set}LayoutPropertytype narrowing (6.0.0-1): Small effort — runbun run typecheckafter bump; expect ≤5 trivial fixes (primarily"visibility"string typing).@maplibre/maplibre-gl-style-specpin (24.8.1): The main motivation for upgrading. Once on v6, all style-spec types are re-exported frommaplibre-glitself and the separate pinned dependency can be dropped. 12 files need a one-line import-source change.addProtocolAPI is stable across v5→v6.See
docs/maplibre-v6-migration.mdfor the full breaking-changes table, file:line touch-point list, open questions, and suggested upgrade order.https://claude.ai/code/session_01DLvs7r6qNfKdqmuzQF4EKr
Generated by Claude Code