Mapbox Maplibre Migration

If you're moving from MapLibre to Mapbox GL JS, this walks through the whole process: swapping dependencies, adding your access token, switching to Mapbox's built-in styles, and updating plugin references. The libraries are 95% API compatible since MapLibre forked from Mapbox v1.13, so most of your code stays identical. What's actually helpful here is the side-by-side comparison of what you gain (official support, premium tiles, no infrastructure to maintain) versus what you give up (open source license, slightly smaller bundle). It covers token security basics and lists all the Mapbox style URLs, which saves you from hunting through docs. Straightforward migration guide that doesn't oversell either option.

skills.sh installs: 1.4K
GitHub stars: 86
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add mapbox/mapbox-agent-skills --skill mapbox-maplibre-migration --agent claude-code

Installs into .claude/skills of the current project.

Files

MapLibre to Mapbox Migration Skill

Expert guidance for migrating from MapLibre GL JS to Mapbox GL JS. Covers the shared history, API compatibility, migration steps, and the advantages of Mapbox's platform.

Understanding the Fork

History

MapLibre GL JS is an open-source fork of Mapbox GL JS v1.13.0, created in December 2020 when Mapbox changed their license starting with v2.0.

Timeline:

Pre-2020: Mapbox GL JS was open source (BSD license)
Dec 2020: Mapbox GL JS v2.0 introduced proprietary license
Dec 2020: Community forked v1.13 as MapLibre GL JS
Present: Both libraries continue active development

Key Insight: The APIs are ~95% identical because MapLibre started as a Mapbox fork. Most code works in both with minimal changes, making migration straightforward.