mirror of
https://github.com/maputnik/editor.git
synced 2026-04-04 08:30:00 +00:00
a23208d60d
Bumps [i18next](https://github.com/i18next/i18next) from 25.10.10 to 26.0.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next/releases">i18next's releases</a>.</em></p> <blockquote> <h2>v26.0.1</h2> <ul> <li>fix: Formatter no longer crashes when <code>alwaysFormat</code> is <code>true</code> and no format specifier is present (<code>format</code> is <code>undefined</code>)</li> <li>fix: Formatter now returns <code>undefined</code>/<code>null</code> values as-is instead of producing <code>NaN</code> when the value is missing</li> </ul> <h2>v26.0.0</h2> <p><strong>This is a major breaking release:</strong></p> <h3>Breaking Changes</h3> <ul> <li><strong>Remove deprecated <code>initImmediate</code> option</strong> — the backward-compatibility mapping from <code>initImmediate</code> to <code>initAsync</code> (introduced in v24) has been removed. Use <code>initAsync</code> instead.</li> <li><strong>Remove legacy <code>interpolation.format</code> function</strong> — the old monolithic format function (<code>interpolation: { format: (value, format, lng) => ... }</code>) is no longer supported. The built-in Formatter (or a custom Formatter module via <code>.use()</code>) is now always used. Migrate to the <a href="https://www.i18next.com/translation-function/formatting">new formatting approach</a> using <code>i18next.services.formatter.add()</code> or <code>.addCached()</code> for custom formatters.</li> <li><strong>Remove console support notice</strong> — the console support notice introduced in v25.8.0 has been removed, along with the <code>showSupportNotice</code> option and all related internal suppression logic (<code>globalThis.__i18next_supportNoticeShown</code>, <code>I18NEXT_NO_SUPPORT_NOTICE</code> env var). See our blog post for the <a href="https://www.locize.com/blog/i18next-support-notice">full story</a>.</li> <li><strong>Remove <code>simplifyPluralSuffix</code> option</strong> — this option was unused by the core PluralResolver (which relies entirely on <code>Intl.PluralRules</code>). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to <code>true</code> internally.</li> <li><strong>Remove deprecated <code>@babel/polyfill</code></strong> from devDependencies.</li> </ul> <h3>Improvements</h3> <ul> <li><strong>Code modernization</strong> across all source files: <ul> <li>Replace <code>indexOf() > -1</code> / <code>indexOf() < 0</code> with <code>.includes()</code> (~40+ occurrences)</li> <li>Replace <code>indexOf() === 0</code> with <code>.startsWith()</code> where appropriate</li> <li>Replace <code>var</code> with <code>const</code>, <code>'' + object</code> with <code>String(object)</code>, <code>.substring()</code> with <code>.slice()</code></li> <li>Replace <code>.apply(observer, [event, ...args])</code> with direct call <code>observer(event, ...args)</code></li> <li>Remove unnecessary <code>.call(this, ...)</code> in BackendConnector retry logic</li> <li>Fix <code>array-callback-return</code> in LanguageUtils <code>getBestMatchFromCodes</code></li> <li>Clean up all stale <code>eslint-disable</code> comments from source files</li> </ul> </li> <li><strong>EventEmitter</strong>: add <code>once()</code> method for one-time event subscriptions</li> <li><strong>Memory leak fix</strong>: move module-level <code>checkedLoadedFor</code> cache to Translator instance, preventing cross-instance state leakage</li> <li><strong>TypeScript</strong>: fix <code>BackendModule</code> generic parameter naming inconsistency between CJS and ESM type definitions</li> <li><strong>TypeScript</strong>: add <code>once()</code> method to <code>i18n</code> and <code>ResourceStore</code> type interfaces</li> <li><strong>ESLint 9</strong>: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with <a href="https://github.com/neostandard/neostandard">neostandard</a></li> <li><strong>Vitest 4</strong>: upgrade from vitest 3 to vitest 4, migrate workspace files to <code>test.projects</code> config</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next/blob/master/CHANGELOG.md">i18next's changelog</a>.</em></p> <blockquote> <h2>26.0.1</h2> <ul> <li>fix: Formatter no longer crashes when <code>alwaysFormat</code> is <code>true</code> and no format specifier is present (<code>format</code> is <code>undefined</code>)</li> <li>fix: Formatter now returns <code>undefined</code>/<code>null</code> values as-is instead of producing <code>NaN</code> when the value is missing</li> </ul> <h2>26.0.0</h2> <p><strong>This is a major breaking release:</strong></p> <h3>Breaking Changes</h3> <ul> <li><strong>Remove deprecated <code>initImmediate</code> option</strong> — the backward-compatibility mapping from <code>initImmediate</code> to <code>initAsync</code> (introduced in v24) has been removed. Use <code>initAsync</code> instead.</li> <li><strong>Remove legacy <code>interpolation.format</code> function</strong> — the old monolithic format function (<code>interpolation: { format: (value, format, lng) => ... }</code>) is no longer supported. The built-in Formatter (or a custom Formatter module via <code>.use()</code>) is now always used. Migrate to the <a href="https://www.i18next.com/translation-function/formatting">new formatting approach</a> using <code>i18next.services.formatter.add()</code> or <code>.addCached()</code> for custom formatters.</li> <li><strong>Remove console support notice</strong> — the console support notice introduced in v25.8.0 has been removed, along with the <code>showSupportNotice</code> option and all related internal suppression logic (<code>globalThis.__i18next_supportNoticeShown</code>, <code>I18NEXT_NO_SUPPORT_NOTICE</code> env var). See our blog post for the <a href="https://www.locize.com/blog/i18next-support-notice">full story</a>.</li> <li><strong>Remove <code>simplifyPluralSuffix</code> option</strong> — this option was unused by the core PluralResolver (which relies entirely on <code>Intl.PluralRules</code>). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to <code>true</code> internally.</li> <li><strong>Remove deprecated <code>@babel/polyfill</code></strong> from devDependencies.</li> </ul> <h3>Improvements</h3> <ul> <li><strong>Code modernization</strong> across all source files: <ul> <li>Replace <code>indexOf() > -1</code> / <code>indexOf() < 0</code> with <code>.includes()</code> (~40+ occurrences)</li> <li>Replace <code>indexOf() === 0</code> with <code>.startsWith()</code> where appropriate</li> <li>Replace <code>var</code> with <code>const</code>, <code>'' + object</code> with <code>String(object)</code>, <code>.substring()</code> with <code>.slice()</code></li> <li>Replace <code>.apply(observer, [event, ...args])</code> with direct call <code>observer(event, ...args)</code></li> <li>Remove unnecessary <code>.call(this, ...)</code> in BackendConnector retry logic</li> <li>Fix <code>array-callback-return</code> in LanguageUtils <code>getBestMatchFromCodes</code></li> <li>Clean up all stale <code>eslint-disable</code> comments from source files</li> </ul> </li> <li><strong>EventEmitter</strong>: add <code>once()</code> method for one-time event subscriptions</li> <li><strong>Memory leak fix</strong>: move module-level <code>checkedLoadedFor</code> cache to Translator instance, preventing cross-instance state leakage</li> <li><strong>TypeScript</strong>: fix <code>BackendModule</code> generic parameter naming inconsistency between CJS and ESM type definitions</li> <li><strong>TypeScript</strong>: add <code>once()</code> method to <code>i18n</code> and <code>ResourceStore</code> type interfaces</li> <li><strong>ESLint 9</strong>: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with <a href="https://github.com/neostandard/neostandard">neostandard</a></li> <li><strong>Vitest 4</strong>: upgrade from vitest 3 to vitest 4, migrate workspace files to <code>test.projects</code> config</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="18b3dbb473"><code>18b3dbb</code></a> 26.0.1</li> <li><a href="c829f91a2a"><code>c829f91</code></a> fix: Formater crashes etc.</li> <li><a href="1593d1125e"><code>1593d11</code></a> remove node v18 from github actions</li> <li><a href="d85c23da86"><code>d85c23d</code></a> 26.0.0</li> <li><a href="fad19d59cf"><code>fad19d5</code></a> feat!: v26.0.0 — major version with breaking changes</li> <li><a href="780aa9170f"><code>780aa91</code></a> jsr update</li> <li>See full diff in <a href="https://github.com/i18next/i18next/compare/v25.10.10...v26.0.1">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Maputnik
A free and open visual editor for the MapLibre GL styles targeted at developers and map designers.
Usage
- 🔗 Design your maps online at https://www.maplibre.org/maputnik/ (all in local storage)
- 🔗 Use the Maputnik CLI for local style development
- In a Docker, run this command and browse to http://localhost:8888, Ctrl+C to stop the server.
docker run -it --rm -p 8888:8000 ghcr.io/maplibre/maputnik:main
To see the CLI options (for example file watching or style serving) run:
docker run -it --rm -p 8888:8000 ghcr.io/maplibre/maputnik:main --help
You might need to mount a volume (-v) to be able to use these options.
Documentation
The documentation can be found in the Wiki. You are welcome to collaborate!
- 🔗 Study the Maputnik Wiki
- 📹 Design a map from Scratch https://youtu.be/XoDh0gEnBQo
Develop
Maputnik is written in typescript and is using React and MapLibre GL JS.
We ensure building and developing Maputnik works with the current active LTS Node.js version and above.
Check out our Internationalization guide for UI text related changes.
Getting Involved
Join the #maplibre or #maputnik slack channel at OSMUS: get an invite at https://slack.openstreetmap.us/ Read the the below guide in order to get familiar with how we do things around here.
Install the deps, start the dev server and open the web browser on http://localhost:8888/.
# install dependencies
npm install
# start dev server
npm run start
If you want Maputnik to be accessible externally use the --host option:
# start externally accessible dev server
npm run start -- --host 0.0.0.0
The build process will watch for changes to the filesystem, rebuild and autoreload the editor.
npm run build
Lint the JavaScript code.
# run linter
npm run lint
npm run lint-css
npm run sort-styles
Tests
For E2E testing we use Cypress
Cypress doesn't start a server so you'll need to start one manually by running npm run start.
Now open a terminal and run the following using chrome:
npm run test
or firefox:
npm run test -- --browser firefox
See the following docs for more info: (Launching Browsers)[https://docs.cypress.io/guides/guides/launching-browsers]
You can also see the tests as they run or select which suites to run by executing:
npm run cy:open
Release process
- Review
CHANGELOG.md- Double-check that all changes included in the release are appropriately documented.
- To-be-released changes should be under the "main" header.
- Commit any final changes to the changelog.
- Run Create bump version PR by manual workflow dispatch and set the version number in the input. This will create a PR that changes the changelog and
package.jsonfile to review and merge. - Once merged, an automatic process will kick in and creates a GitHub release and uploads release assets.
Sponsors
Thanks to the supporters of the Kickstarter campaign. This project would not be possible without these commercial and individual sponsors. You can see this file's history for previous sponsors of the original Maputnik repo. Read more about the MapLibre Sponsorship Program at https://maplibre.org/sponsors/.
License
Maputnik is licensed under MIT and is Copyright (c) Lukas Martinelli and Maplibre contributors. As contributor please take extra care of not violating any Mapbox trademarks. Do not get inspired by other map studios and make your own decisions for a good style editor.