Repository navigation
Releases
Release v0.86.2
Verbaly has its own home on GitHub: github.com/verbaly-i18n. The project moves from a personal account to an organization with two maintainers, and every old link still works. Breaking: nothing.
Highlights
- The code lives at github.com/verbaly-i18n/verbaly. The links on npm, in the READMEs and in your AI assistant's plugin now go there. Old links keep working: GitHub sends them to the new place.
- Two maintainers. Verbaly is now looked after by two people, so releases, reviews and security reports no longer depend on one.
- A new name in the official MCP catalog. The Verbaly server is listed as
io.github.verbaly-i18n/verbaly, and the old entry points to it. The package you install,@verbaly/mcp, keeps its name. - Nothing changes in your project. The code you install is, byte for byte, the code of 0.86.1. You can update without checking anything.
For the full details of this release, see the repository changelog.
Release v0.86.1
Verbaly has its own address: verbaly.dev. The documentation moves there, and every old link still takes you to the same page. Breaking: nothing.
Highlights
- The documentation lives at verbaly.dev. The links on npm, on GitHub and in your AI assistant's plugin now go there. Old links keep working: they take you to the same page at the new address.
- A plugin for Cursor. The plugin that adds Verbaly to Claude Code now works in Cursor too, with the same tools and the same rules for your assistant.
- Nothing changes in your project. The code you install is, byte for byte, the code of 0.86.0. You can update without checking anything.
For the full details of this release, see the repository changelog.
Release v0.86.0
The same Verbaly, harder to break by accident. Nothing changes in your project: this release adds checks on our side, so a mistake in Verbaly's own code is caught before it is published. Breaking: nothing.
Highlights
- Nothing changes in your project. The code that reads your files is, byte for byte, the code of 0.85.0. You can update without checking anything.
- A change in the tool Verbaly reads your code with now stops us, not you. Verbaly reads your files with a tool made by another team. If a new version of that tool renames something, Verbaly now fails to build on our side, where before it could have missed text in your project without saying so.
- A new kind of problem cannot be left out of a report.
verbaly check, your build,verbaly doctorand your AI assistant all list the same problems, and a test now fails when one of them forgets a kind the others report.
For the full details of this release, see the repository changelog.
Release v0.85.0
A translation run that gets cut keeps what it finished, and Verbaly installs in your AI assistant with one command. Until now a run that stopped halfway lost every answer it already had, and a file that could not be saved left machine translations looking reviewed. Breaking: nothing for a project. One change for code that calls the compiler: translateProject no longer rejects when a translation file cannot be saved, it reports that language in failed and goes on.
Highlights
- A translation run that stops halfway keeps the languages it finished. Closing the terminal or losing the connection used to throw away every answer the run already had. Each language is now saved the moment it is complete, and running it again only asks for what is left.
- A machine translation can no longer pass as reviewed. When a file could not be saved in the middle of a run, the languages written before it lost their "waiting for review" mark. The mark is now saved before the text.
- One language that cannot be saved no longer stops the others. The run finishes, saves the rest and names the language that failed, with the reason.
- Verbaly installs in Claude Code with one plugin.
claude plugin marketplace add AronSoto/verbaly, thenclaude plugin install verbaly@verbaly, and your assistant gets the tools and the rules together. Gemini CLI takes the same pair withgemini extensions install https://github.com/AronSoto/verbaly.
For the full details of this release, see the repository changelog.
Release v0.84.0
Starting a language is creating an empty file, and a mistyped language is said out loud. The small gaps the last audit left open are closed: each one made Verbaly answer something that was not quite true. Breaking: nothing for a project. One change for code that calls the compiler: targetLocales(cfg, names) throws for a name the project does not have, where it used to drop it.
Highlights
- A new language starts with an empty file. Creating
locales/fr.jsonwith nothing in it used to stop every command with an error. Now it is a language with nothing translated yet, and it is written in the same shape as your main translation file. - A mistyped language is an error, not "nothing to do". An AI assistant that asked to translate into
essinstead ofeswas told there was nothing left to translate. It now gets the list of your languages and how to start a new one. - Text in
.cjsand.ctsfiles is found. A server written in CommonJS keeps its text insrc/like any other file, and Verbaly used to skip those files. verbaly rendersays when it skips a folder. A folder named like your main language, such asdist/en/, is never copied into the other languages, and until now nothing told you.- Before you update: if
src/orapp/hold.cjsor.ctsfiles with text, that text is extracted from now on, soverbaly checkasks for its translations.
For the full details of this release, see the repository changelog.
Release v0.83.0
Faster on Windows, and the same site as before. Verbaly's inside was reorganized so each part does one job, and every project it was checked against builds, checks and renders exactly as with 0.82.0. Breaking: nothing.
Highlights
- Starting your dev server or a build takes less time on Windows. Verbaly now reads your files several at a time there, and reading them one by one was most of its wait. Other systems keep the way that was already fastest for them.
- A folder that looks like your translations folder no longer reloads your pages. Saving a file in a copy such as
locales-old/, or in a folder insidelocales/, refreshed every open tab during development, as if a translation had changed. - Each package page on npm says what it works with. It names the framework versions or the Node version it needs, and links to the tests, the security score and the proof of where it was built.
- Studio names every check of your project in plain words. Eight of them showed an internal name, such as
source texts.
For the full details of this release, see the repository changelog.
Release v0.82.0
Files from your translators load however their tool wrote them, and a project can leave another translation library one component at a time. Every package was read line by line for this release, and what it found at the edges is fixed. Breaking: a command told to work on a language your project does not have now stops with an error, where it used to go on.
Highlights
- Files from your translators load however their tool saved them. A spreadsheet saved with semicolons or tabs imports like one with commas, and so does a translation file written with single quotes. Before, those files were refused or arrived empty.
- Move from another translation library one component at a time. Text a component still takes from react-i18next, Lingui, next-translate or ttag is left exactly as you wrote it. Before, the build could rewrite it and break that page.
- A mistyped language name is caught.
npx verbaly review --locale essused to answer that nothing was waiting for review. Now it stops, lists the languages your project has and says how to start a new one. - The text wrapping command only writes where the result works.
npx verbaly wrap --writeleaves a file alone when the text it would wrap cannot reacht, and tells you the line to add. Before, a list written astabs.map((t) => …)was enough for it to write code that did not run. - Before you update: if a script of yours passes
--localeswith a language the project does not have yet, add that language tolocalesin your config first, or create its translation file holding{}.
For the full details of this release, see the repository changelog.
Release v0.81.0
Getting started now names everything your app needs, whatever it is built with, and every release is tried first on each framework's official starter app. Nothing you already wrote has to change. Breaking: nothing.
Highlights
- The setup command names every package your app needs. In a Vite or webpack app with Vue, React or Svelte,
npx verbaly initnow lists the package for your framework too. Before, the install it showed left your first import broken. - The text wrapping command sends a Vue project to the right package. When
npx verbaly wrapcannot change a file yet, it says which package gives that file itst, to you and to coding agents. Before, it always named React. - The SvelteKit and Next.js guides on npm say how the language is chosen. The address decides first when it carries a language, then the visitor's saved choice, then the browser.
- Each release is tried on every framework's official starter app. Before it ships, Verbaly goes into the starter apps of Vite, SvelteKit, Next.js, Nuxt and Astro, and each one is built and read in two languages.
For the full details of this release, see the repository changelog.
Release v0.80.0
Following the README now works the first time in every framework, and the language a visitor picks stays picked. Nothing you already wrote has to change. Breaking: nothing.
Highlights
- A page with no provider shows your text. In a Vite or webpack app, a component that only used
useT()came out as a blank page. Now Verbaly loads your languages by itself. - Every install line works as written. The Svelte and SvelteKit steps left
npx verbalywithout a command, and Astro's first example did not build. Both are fixed, and each README installs what its own code needs. - The language a visitor picks stays picked. A language menu built on
useLocalenow updates the page language and remembers the choice. An Astro site with its own language addresses now goes to the right one. - The file TypeScript reads keeps all your texts. Running
svelte-check, your tests or the dev server used to remove the texts that no translation file had yet. - A translation can no longer run as code in a generated page. A translation file made on purpose could reach a script in the static pages Verbaly writes. Now it stays text.
For the full details of this release, see the repository changelog.
Release v0.79.0
A fresh copy of your project checks its types after its first build, and coding agents know which Verbaly tools change files. Nothing you already wrote has to change. Breaking: nothing.
Highlights
- A fresh copy of your project checks its types after the first build. Building with Vite, SvelteKit, webpack, Rollup, esbuild or Rspack now writes the file TypeScript reads for your texts. Before, only the dev server and Next wrote it.
- Coding agents pick the right Verbaly tool. Each tool says whether it only reads or changes files, and names the one to use instead when another fits better.
- A mistyped command gets a clear answer. Typing
verbaly constructornow says the command does not exist, instead of showing a JavaScript error.
For the full details of this release, see the repository changelog.