dependabot[bot]
a16d38abba
Bumps [i18next-cli](https://github.com/i18next/i18next-cli) from 1.72.1 to 1.73.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next-cli/blob/main/CHANGELOG.md">i18next-cli's changelog</a>.</em></p> <blockquote> <h2>1.73.0</h2> <ul> <li>feat: <code>init</code> runs without the wizard. <code>--yes</code> takes the detected defaults for every question not answered by <code>--locales</code>, <code>--input</code>, <code>--output</code>, <code>--backend <local|locize|other></code> or <code>--file-type <ts|js></code>; <code>--project-id <id></code> (or <code>LOCIZE_PROJECTID</code>) supplies the Locize project id and skips the signup page and the credential prompts. Made for scripts and AI coding agents, which cannot drive the prompts.</li> <li>feat: <code>init --agent-note</code> (also the last wizard question, default No) appends a short <code>## Internationalization</code> section to <code>AGENTS.md</code> (and <code>CLAUDE.md</code> when present; when neither exists, <code>AGENTS.md</code> is created, plus a <code>CLAUDE.md</code> importing it if the project has a <code>.claude/</code> folder) so the next agent session knows where the locale files are and how translations are managed. The exact text is in the README; <code>--no-agent-note</code> skips the question. Nothing is written unless you say yes.</li> <li>change: the <code>localize</code> agent prompt (<code>--print-agent-prompt</code>) and the <code>i18next-localization</code> skill no longer presume Locize. The agent asks the developer once, before creating the config, whether to manage the translations with Locize or keep the files in the repository, and never creates a project or asks for an API key unless they chose Locize. The prompt now creates the config with <code>init --yes ...</code> instead of the interactive wizard.</li> </ul> <h2>1.72.4</h2> <ul> <li>docs: the README shows the skills.sh install badge for the <code>i18next-localization</code> Agent Skill, and <code>i18next-cli --help</code> now ends with a one-line hint on installing it (<code>npx skills add i18next/i18next-cli</code>). No other command prints anything new.</li> </ul> <h2>1.72.3</h2> <ul> <li>feat(funnel): the Locize hint after <code>status</code>, <code>extract</code> and <code>sync</code> is now a single line that names the untranslated-key gap and the one command that fills it (<code>npx i18next-cli localize</code>), each with its own <code>?from=</code> tagged register link. It only appears when secondary locales actually have untranslated keys; the 24h cooldown and the CI/non-TTY suppression are unchanged.</li> </ul> <h2>1.72.2</h2> <ul> <li>fix: extract dynamic keys built from <code>for...of</code> loop variables. <code>for (const unit of UNITS)</code> over an <code>as const</code> string array now binds <code>unit</code> while the loop body is walked, just like <code>.map()</code> / <code>.forEach()</code> callback parameters already did.</li> <li>fix: capture <code>as const</code> arrays of object literals (e.g. <code>[{ unit: 'day' }, { unit: 'hour' }]</code>), so both <code>for (const { unit } of UNITS)</code> and <code>UNITS.forEach(({ unit }) => ...)</code> resolve the destructured properties.</li> <li>fix: resolve object destructuring of a known <code>as const</code> object, e.g. <code>const { unit } = rate;</code> followed by <code>t(`msg ${unit}`)</code> (<a href="https://redirect.github.com/i18next/i18next-cli/issues/289">#289</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/i18next/i18next-cli/commit/bf7f167b61e8578bf78022578088b18a28f6381a"><code>bf7f167</code></a> 1.73.0</li> <li><a href="https://github.com/i18next/i18next-cli/commit/8a38aa0606e318556bf12c6e0101d0dd0d8244de"><code>8a38aa0</code></a> feat(init): non-interactive options, --project-id and an opt-in agent note; t...</li> <li><a href="https://github.com/i18next/i18next-cli/commit/7fb1095445516f7aa745ce5fe1682a2fe6e3ad3f"><code>7fb1095</code></a> docs(skill): single-line description in the SKILL.md frontmatter</li> <li><a href="https://github.com/i18next/i18next-cli/commit/9224c6eff8b98e32c7fffcb136ffd0be916e8c6c"><code>9224c6e</code></a> 1.72.4</li> <li><a href="https://github.com/i18next/i18next-cli/commit/dcd02988c4da0bc746be0902e71f58f45db9f13e"><code>dcd0298</code></a> docs: skills.sh badge and a --help hint for the i18next-localization skill</li> <li><a href="https://github.com/i18next/i18next-cli/commit/285716dc3e6f4328866f7ae568ee8ace76dc8e11"><code>285716d</code></a> 1.72.3</li> <li><a href="https://github.com/i18next/i18next-cli/commit/ce1c77dc350d605540304e34fed5361de7bcab04"><code>ce1c77d</code></a> feat(funnel): one-line Locize hint after status, extract and sync</li> <li><a href="https://github.com/i18next/i18next-cli/commit/87103c7ea6f3fecd01376b28fe6127ee341de7bd"><code>87103c7</code></a> 1.72.2</li> <li><a href="https://github.com/i18next/i18next-cli/commit/bb1c07e2589900c44c0ee7a7f598afefc57a2b77"><code>bb1c07e</code></a> fix: extract dynamic keys from for-of loops and destructured as-const objects</li> <li>See full diff in <a href="https://github.com/i18next/i18next-cli/compare/v1.72.1...v1.73.0">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
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
- 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.