dependabot[bot] c64452c1bd chore(deps): Bump i18next from 26.5.3 to 26.5.6 (#2264)
Bumps [i18next](https://github.com/i18next/i18next) from 26.5.3 to
26.5.6.
<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.5.6</h2>
<ul>
<li>fix: <code>cloneInstance({ forkResourceStore: true })</code> now
copies the resources at every level. It copied them only down to the
namespace objects, so nested keys and arrays stayed shared with the
original instance: <code>addResource()</code> with a nested key
(<code>fork.addResource('en', 'translation', 'greeting.hello',
'Hi')</code>) or a deep <code>addResourceBundle()</code> on the fork
also changed the original instance and every other fork. Flat keys were
already isolated. Forking a large store takes a bit longer: with 300k
keys in nested groups, about 11 ms instead of 3 ms per fork. Clones
without <code>forkResourceStore</code> still share the store as before.
Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2456">#2456</a>,
follow-up to <a
href="https://redirect.github.com/i18next/i18next/issues/2270">#2270</a>).</li>
</ul>
<h2>v26.5.5</h2>
<ul>
<li>fix: with the default <code>skipOnVariables: true</code>, a
<code>{{placeholder}}</code> inside a value inserted with an unescaped
<code>{{- var}}</code> now stays literal, as it already did for
<code>{{var}}</code>. The escape pass ran after the unescaped values
were written and scanned them again, so <code>t('{{- a}}', { a: '{{b}}',
b: 'c' })</code> returned <code>'c'</code> instead of
<code>'{{b}}'</code>. With pre-built HTML that carries user text, like
<code>t('You may contact {{name}} at {{- emailHTML}}.', { name,
emailHTML })</code>, that text could pull another variable of the same
<code>t()</code> call into the output. Results with
<code>skipOnVariables: false</code>, and values without placeholders,
are unchanged. Compatibility note: a <code>{{- var}}</code> value whose
placeholders were meant to be filled from the same <code>t()</code> call
now keeps them literally; <code>skipOnVariables: false</code> restores
the old behavior. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2455">#2455</a>,
reported in <a
href="https://redirect.github.com/i18next/i18next/issues/1595#issuecomment-814611747">#1595</a>).</li>
</ul>
<h2>v26.5.4</h2>
<ul>
<li>fix: with the default <code>skipOnVariables: true</code>, a
<code>{{placeholder}}</code> inside an interpolated value now stays
literal also when the same placeholder appears later in the translation.
Each value was written with <code>String.replace</code>, which replaces
the first copy of the placeholder text, and that could be the copy
inside an earlier value: <code>t('{{name}} has {{count}} items', { name:
'{{count}}', count: 5 })</code> returned <code>'5 has {{count}}
items'</code> instead of <code>'{{count}} has 5 items'</code>. The value
is now written at the position of the matched placeholder. Results with
<code>skipOnVariables: false</code> are unchanged. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2454">#2454</a>,
reported in <a
href="https://redirect.github.com/i18next/i18next/issues/1595#issuecomment-814609503">#1595</a>).</li>
<li>fix: with <code>useRawValueToEscape: true</code>, a non-string value
in an unescaped <code>{{- var}}</code> placeholder or with
<code>escapeValue: false</code> no longer throws <code>val.replace is
not a function</code>; it is converted to a string like any other
value.</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.5.6</h2>
<ul>
<li>fix: <code>cloneInstance({ forkResourceStore: true })</code> now
copies the resources at every level. It copied them only down to the
namespace objects, so nested keys and arrays stayed shared with the
original instance: <code>addResource()</code> with a nested key
(<code>fork.addResource('en', 'translation', 'greeting.hello',
'Hi')</code>) or a deep <code>addResourceBundle()</code> on the fork
also changed the original instance and every other fork. Flat keys were
already isolated. Forking a large store takes a bit longer: with 300k
keys in nested groups, about 11 ms instead of 3 ms per fork. Clones
without <code>forkResourceStore</code> still share the store as before.
Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2456">#2456</a>,
follow-up to <a
href="https://redirect.github.com/i18next/i18next/issues/2270">#2270</a>).</li>
</ul>
<h2>26.5.5</h2>
<ul>
<li>fix: with the default <code>skipOnVariables: true</code>, a
<code>{{placeholder}}</code> inside a value inserted with an unescaped
<code>{{- var}}</code> now stays literal, as it already did for
<code>{{var}}</code>. The escape pass ran after the unescaped values
were written and scanned them again, so <code>t('{{- a}}', { a: '{{b}}',
b: 'c' })</code> returned <code>'c'</code> instead of
<code>'{{b}}'</code>. With pre-built HTML that carries user text, like
<code>t('You may contact {{name}} at {{- emailHTML}}.', { name,
emailHTML })</code>, that text could pull another variable of the same
<code>t()</code> call into the output. Results with
<code>skipOnVariables: false</code>, and values without placeholders,
are unchanged. Compatibility note: a <code>{{- var}}</code> value whose
placeholders were meant to be filled from the same <code>t()</code> call
now keeps them literally; <code>skipOnVariables: false</code> restores
the old behavior. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2455">#2455</a>,
reported in <a
href="https://redirect.github.com/i18next/i18next/issues/1595#issuecomment-814611747">#1595</a>).</li>
</ul>
<h2>26.5.4</h2>
<ul>
<li>fix: with the default <code>skipOnVariables: true</code>, a
<code>{{placeholder}}</code> inside an interpolated value now stays
literal also when the same placeholder appears later in the translation.
Each value was written with <code>String.replace</code>, which replaces
the first copy of the placeholder text, and that could be the copy
inside an earlier value: <code>t('{{name}} has {{count}} items', { name:
'{{count}}', count: 5 })</code> returned <code>'5 has {{count}}
items'</code> instead of <code>'{{count}} has 5 items'</code>. The value
is now written at the position of the matched placeholder. Results with
<code>skipOnVariables: false</code> are unchanged. Thanks <a
href="https://github.com/nk-batman21"><code>@​nk-batman21</code></a> (<a
href="https://redirect.github.com/i18next/i18next/pull/2454">#2454</a>,
reported in <a
href="https://redirect.github.com/i18next/i18next/issues/1595#issuecomment-814609503">#1595</a>).</li>
<li>fix: with <code>useRawValueToEscape: true</code>, a non-string value
in an unescaped <code>{{- var}}</code> placeholder or with
<code>escapeValue: false</code> no longer throws <code>val.replace is
not a function</code>; it is converted to a string like any other
value.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/i18next/i18next/commit/82894c159845c3675fb6540db52a4144abbd5d4a"><code>82894c1</code></a>
26.5.6</li>
<li><a
href="https://github.com/i18next/i18next/commit/343080da6802c0badb2fe1032139d49af93d9774"><code>343080d</code></a>
build</li>
<li><a
href="https://github.com/i18next/i18next/commit/8e2eebb132aaccfb752990b6cc61cbfd7d835764"><code>8e2eebb</code></a>
changelog for 26.5.6</li>
<li><a
href="https://github.com/i18next/i18next/commit/822a37bc57f50b4a476aa630f864d3ed1f88a7e9"><code>822a37b</code></a>
fix: copy nested resources when cloning with forkResourceStore (<a
href="https://redirect.github.com/i18next/i18next/issues/2456">#2456</a>)</li>
<li><a
href="https://github.com/i18next/i18next/commit/744c5cb41a19f52ae08d1a71c2d9ceca6525dc1d"><code>744c5cb</code></a>
26.5.5</li>
<li><a
href="https://github.com/i18next/i18next/commit/de5960eee00d9db2a7c1b452d6ce9231c16b6474"><code>de5960e</code></a>
build</li>
<li><a
href="https://github.com/i18next/i18next/commit/fbe16f3429273f2f9c1fe9736f4590fa2e8253a5"><code>fbe16f3</code></a>
changelog for 26.5.5</li>
<li><a
href="https://github.com/i18next/i18next/commit/67b4ae194ed4a1af083119f77daba48f1c295f1d"><code>67b4ae1</code></a>
fix: keep placeholders inside unescaped values literal (<a
href="https://redirect.github.com/i18next/i18next/issues/2455">#2455</a>)</li>
<li><a
href="https://github.com/i18next/i18next/commit/aadd75ba9e88a20b34b7f44798d4e3bd8ec71baa"><code>aadd75b</code></a>
26.5.4</li>
<li><a
href="https://github.com/i18next/i18next/commit/a43c43286a381bbae144c04de9f8056f464c7cd9"><code>a43c432</code></a>
build</li>
<li>Additional commits viewable in <a
href="https://github.com/i18next/i18next/compare/v26.5.3...v26.5.6">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>
2026-10-26 14:26:02 +00:00
2019-08-03 12:08:54 -04:00
2016-12-03 17:03:39 +01:00
2025-01-21 09:54:19 +01:00
2018-10-20 18:35:35 +02:00
2026-07-12 15:46:30 +03:00
2023-12-20 07:18:13 +02:00
2025-02-25 05:01:15 -05:00
2025-02-25 05:01:15 -05:00
2026-07-12 15:46:30 +03:00

Maputnik logo

Maputnik

GitHub CI status License

A free and open visual editor for the MapLibre GL styles targeted at developers and map designers.

Usage

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!

Design Map from Scratch

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

End-to-end tests

For E2E testing we use Playwright. The tests live in the e2e directory and drive the app through the MaputnikDriver page object.

The first time you run the tests, install the browser:

npx playwright install chromium

Playwright automatically starts the dev server (npm run start) for you, so you can just run:

npm run test

Some useful options:

# see the tests run in a headed browser
npm run test -- --headed

# run a single spec / filter by title
npm run test -- e2e/map.spec.ts
npm run test -- -g "zoom level"

# open the interactive UI mode
npx playwright test --ui

Running the E2E tests also produces a code-coverage report in coverage/ (collected via istanbul instrumentation of the dev server).

Unit & component tests

Unit tests and component tests run with Vitest; component tests (*.browser.test.tsx) use Vitest's browser mode with the Playwright provider.

npm run test-unit

Release process

  1. 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.
  2. 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.json file to review and merge.
  3. 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.

S
Description
An open source visual editor for the 'Mapbox Style Specification'
Readme
290 MiB
Languages
JavaScript 88.5%
SCSS 9.3%
CSS 1.2%
HTML 0.9%
Dockerfile 0.1%