Changelog · Verbaly

0.45.0

Latest release2026-08-28

A catalog only grows, and every page was paying for all of it

Text that lives on one page, a list of releases, a blog archive, a long list of questions, was downloaded by every visitor on every page. This version lets you name those groups of messages and keep them in the build. The pages that use them still come out translated, because that text is already written into the HTML, and the browser stops downloading it. Looking for the proof also uncovered a real defect underneath. After its first pass, Verbaly could replace correct translated text on the page with the message’s internal name whenever a message was missing. That is fixed here, and it matters to anyone who pre-renders their site.

Highlights

Text that only one page needs stops travelling to all of them. Name that group of messages in your config and the browser no longer downloads it. The pages that use it still come out translated, because that text is already in the HTML.
Pre-rendered text is never destroyed any more. If a message is missing, Verbaly keeps the text that is already on the page instead of replacing it with the message’s internal name. Before, that could happen a moment after a page loaded.
Measured on this site: the file every page loads went from 46.3 KB to 33.5 KB compressed, and the Spanish and Portuguese trees dropped about 14 KB each. Nothing was lost on screen.
Nothing changes if you do not switch it on. It is a new option, and a project that does not write it behaves exactly as before.
The build tells you when it looks wrong, naming a group that matches nothing in your catalog, or one your code reads directly.

Full release notesEvery bullet, per package, in the repo changelog.

0.44.0

Release2026-08-28

Our own checks were measuring the machine, not the code

The job that checks our test coverage was failing at random, and the cause was not a slow test. A test that runs in 22 milliseconds was being failed by a 5 second limit, because that limit counts real time and our test command starts twelve processes on the same processor cores. Twice, that blocked a release. This version fixes it at the root, and spends the rest of its time on the same idea applied to our supply chain: what our build is allowed to do, which tools it runs exactly, and code that could never run at all. Nothing about the package changes.

Highlights

Nothing you install changes. The runtime is identical to 0.43.0 and every published API behaves the same. This release is about the machinery that checks us.
Our build stopped failing at random. Our test suite could fail a perfectly healthy test just because the machine was busy, and twice that blocked a release.
Every tool our build runs is pinned to an exact commit. A tag can be moved by whoever owns it, but a commit cannot, so nothing can quietly change what builds your package.
The job that publishes releases asks for write access only where it needs it, instead of granting it to the whole workflow.
Static analysis runs on every change, and its configuration now lives in our repository, pinned and readable, instead of being a setting only we could see.

Full release notesEvery bullet, per package, in the repo changelog.

0.43.0

Release2026-08-27

Everything we say about ourselves is true again

The badge on our README has said ~3KB since the beginning, while the runtime was actually 3.68 KB. Rather than weaken the claim, this release removes the last piece heavy enough to be worth removing: relative time formatting is 318 bytes that most apps never write, and it now travels only when one of your messages asks for it. The rest of the release is the same idea pointed at everything else the project says about itself.

Highlights

The runtime is 3.00 KB. Relative time formatting joins ICU as something that ships only when one of your messages actually uses it, and there is nothing for you to configure.
A formatter you write yourself now knows which message it was called for. It receives the parameter name and the message key, so its own errors can say where they happened, which was not possible before.
The security policy covers all twelve packages, not the seven that existed when it was written, and it now explains how to verify that a release really came from our CI.
Our security posture is something you can check instead of something we claim: a score from the OpenSSF runs on every change and the badge on the README reads it.

Full release notesEvery bullet, per package, in the repo changelog.

0.42.0

Release2026-08-27

A smaller runtime for everyone who never needed ICU

Verbaly’s own syntax covers plurals, selects and formats, and ICU message syntax is the way out for what it does not. That escape hatch was always described as something you opt into, and it never was: the parser went into every app whether or not a single message used it. Our own documentation site has no ICU messages at all and shipped it on every page. Verbaly already reads your catalogs, so now it only sends the parser where a message actually needs one.

Highlights

The runtime is 11% smaller for anyone who does not use ICU syntax, which is most projects. The parser only ships when one of your messages actually needs it, and there is nothing for you to switch on.
Nothing changes if you do use ICU. Verbaly sees it in your catalogs and brings the parser along, exactly as before.
A message that reaches your app after the build and uses ICU now shows its own text and says why, instead of half-rendering into something that looks almost right. If your text comes from a CMS, one setting ships the parser anyway.

Full release notesEvery bullet, per package, in the repo changelog.

0.41.0

Release2026-08-27

One line to switch, and your choice finally sticks

Verbaly shipped a complete language switcher for one way of doing addresses and a spare part for the other, so every project wrote the second one by hand, ours included. Rewriting our own site on the library’s own helper found a bug that had been there since the switcher moved into the runtime: someone who picked a language was sent back to their browser’s language on the next page load. The other half is that Verbaly had started assuming you wanted the language in your addresses; now it reads your setup instead of guessing.

Highlights

Switching language is one line now, and it is the same line whichever way your addresses work. It goes to the other address when the language lives there, and changes the text where it stands when it does not.
Your choice of language survives the next page load. Picking English on a Spanish page could send you straight back to Spanish, because the switch remembered your choice in one place and the page that greets you read another.
Verbaly stops assuming you want the language in your addresses. It reads your setup: build a version of your site per language and you get addresses per language, otherwise one address serves all of them. You only write it down to disagree.
verbaly doctor tells you whether it read your choice or worked it out, so a setting nobody wrote down never looks like a decision somebody made.
The size check now measures what a real app actually ships, instead of only the smallest possible import and the largest impossible one.

Full release notesEvery bullet, per package, in the repo changelog.

0.40.0

Release2026-08-27

Say where the language lives, and translate the head too

Verbaly has had two ways to carry a language for a long time and never named either of them, so which one you got was decided by whether you remembered to pass an optional field. Naming them turned up the thing that made the naming matter: a page could be translated everywhere a visitor looks and still tell a search engine it is in English, because the title and the description live in the head where nobody reads them. Our own documentation shipped 27 of 27 pages that way.

Highlights

You can now say where the language lives in your addresses, once, in the config: /docs and /es/docs, a prefix on every language, or one address for all of them. Before this the answer depended on which helper you called and what you passed it.
The language switcher is one line and cannot be written wrong. Verbaly hands you a helper that already knows your languages, your source and your mode, and the same line keeps working if you change your mind about the mode.
Your page title and description get translated too. They live in the head, nobody reads them on the page, and they are what a search result shows, so a page could look fully translated and still be listed in English.
verbaly render counts the pages whose title still never changes and tells you once, with the fix. It never fails a build: a product name is allowed not to translate.
verbaly doctor tells you which mode your addresses are in, and says so when your settings ask for two things that cannot both be true.
Breaking: asking for a path without naming your source language no longer compiles. It used to put a prefix on every language including your own, quietly, which was almost never what anyone wanted.

Full release notesEvery bullet, per package, in the repo changelog.

0.39.0

Release2026-08-27

Translating survives a bad connection, and agents get the whole cycle

Verbaly has let a coding agent run it for a while, but only four of its twelve commands were ever handed over, and the two missing ones are the first two an agent needs: finding out what is wrong with a project, and wrapping the text already written in it. Looking at that turned up something worse next door. verbaly translate is the one command that costs money and minutes, and a single bad answer threw the whole run away: batches that had already been paid for and translated were never written to disk.

Highlights

verbaly translate no longer loses work it already paid for. A request that does not come back is tried again, and if it still fails the run keeps going and saves everything else. Running it again asks only for what is left, instead of paying for all of it a second time.
Translating is about four times faster. Requests now go out together instead of one after another, and a long run tells you what has landed while it runs rather than staying silent for minutes.
You can say what must never be translated. Put your product names and any wording you have settled on in translate.glossary, and how you address the reader in translate.instructions, instead of fixing the same word by hand after every run.
Your coding agent gets the two tools it was missing: one to work out why a project is not working, and one to find text written straight into your components and wrap it. Bringing an existing app to Verbaly no longer needs a terminal.
Agents read numbers now, not sentences. Every tool answers with plain data as well as text, so an agent stops guessing at wording that can change between releases.
Accepting a machine translation is still something only a person can do, and that has not changed.

Full release notesEvery bullet, per package, in the repo changelog.

0.38.0

Release2026-08-15

Translations written as groups are safe everywhere

You can keep your translations as nested groups instead of one long flat list, and Verbaly has read that shape for a while. Only half of it did: the commands that write your catalogs read the group names as if they were messages. So extract added a second copy of every message, --prune removed whole groups with every translation inside them, exports reached your translator broken, and translate said there was nothing to do about an app that was half untranslated. Nothing changes for a flat catalog.

Highlights

Translations kept in groups are safe from end to end. Every command now reads and writes them the same way, and your file keeps the shape you gave it instead of being flattened behind your back.
verbaly extract --prune no longer deletes translations. On a catalog written as groups it read each group name as one message, did not recognise it, and removed the whole group with every translation inside it.
Your translator files stop arriving broken. Exporting wrote [object Object] where the text should have been, and verbaly translate reported nothing to do while verbaly status said half the app was untranslated.
A language you add later matches the rest. A new catalog takes the shape of the ones you already have, so a project never ends up half grouped and half flat.
The tool counts in real English. It used to say 1 messages, 1 locales and 1 pages in nine places.
A repeated warning says itself once. A key collision was announced three times in a single verbaly extract, one of them after the summary had already printed.

Full release notesEvery bullet, per package, in the repo changelog.

0.37.0

Release2026-08-10

Your saved language survives a refresh

The last version named the two ways a site can carry its language. Writing the page that explains them turned up the reason one of them had never really worked: if your app keeps one address per page and loads languages on demand, Verbaly knew which language the visitor wanted and simply never fetched it. One line, and the example in our own docs had been showing it all along.

Highlights

A saved language now survives a refresh on a site that keeps one address. A returning visitor used to get the source language back every time, with nothing in the console to explain it.
Nothing changes if your language is in the address, which is what the last two versions were about. This was only ever broken where the language comes from storage or the browser.
A warning that used to give impossible advice now gives the right one. When your page says one language and Verbaly is in another, it told you to read the language from the address. On a site that keeps one address there is nothing to read.
React, Vue and Svelte were each checked against a language that arrives after the page is already on screen. That used to be a rare path and is now the normal one.

Full release notesEvery bullet, per package, in the repo changelog.

0.36.0

Release2026-08-09

Your visitors reach their language on their own

Verbaly publishes your site in every language, each at its own address. The last version made those pages right, and this one is about getting people to them, and about asking from your own code which language a page belongs to. Both were things every project had to write by hand, this site twice in one day. It also fixes a way a page name could be mistaken for a language.

Highlights

Asking which language a page is in no longer needs a helper of your own. Verbaly answers with the language in the address, or with nothing when the address does not carry one. That is a different question from what a visitor prefers, and mixing the two is what let a saved preference paint the wrong language over a page.
Verbaly can send a visitor to their language now. Turn it on and someone landing on your home page goes to your site in their language before anything is drawn. Only the home page, so a search engine still reaches every page of your site directly.
A site served from a subfolder works. Tell Verbaly the folder and the links inside each language point where they should, instead of quietly pointing nowhere.
A page called /es-la-guia is a page, not Spanish. Verbaly read the start of an address a little too eagerly, so a page whose name began like a language code could be translated into it. Now only a real language code counts.
What this version does not change: an app with one address per page works exactly as before. Everything here is for sites where each language has its own address.

Full release notesEvery bullet, per package, in the repo changelog.

0.35.0

Release2026-08-08

Your pre-translated pages stop flickering

Verbaly publishes your static site in every language, under /es/ and /pt/. This version is about what happened to someone who reached one of those pages: it arrived in Spanish and then flashed to English before settling back, nothing told the runtime it was already on a Spanish page, and every link pointed back out. The page was right and everything between it and the visitor was not.

Highlights

A pre-translated page stops flashing into English. Verbaly served the Spanish page and then painted the English text over it until the Spanish catalog finished loading, on exactly the pages this feature exists to keep still.
Landing on /es/ is now enough. Verbaly reads the prefix it wrote itself before it looks at storage or at the browser, because the page you are looking at is already in that language.
Each language stops being an island. Its links pointed at the site root, so arriving in Spanish and clicking once took you back to English. Links to pages that language also has now stay inside it.
Your language switcher sends someone to your site in that language. That is the address they can share and the one search engines index, and the page arrives already translated so nothing flickers. In an app with one address per page, changing the language still just changes the text, exactly as before.
What this version does not do: it does not route anyone anywhere. Someone who lands on your root is being served the source language, and sending them to their language is one rule in your host settings.

Full release notesEvery bullet, per package, in the repo changelog.

0.34.0

Release2026-08-08

What the build gate cannot see

The build gate refuses to build when a translation cannot render what your source renders, but it only ever sees what is in your project at build time. This version goes after everything that arrives later: a catalog that comes from a content system, a source file Verbaly could not read, and a line break inside a rich message that the pre-rendered page and the browser disagreed about. Four real bugs, each one a way to ship something wrong with every command green.

Highlights

A line break inside a rich message no longer doubles in a pre-rendered page. Verbaly wrote it in a way that browsers read as two line breaks, and the page then replaced them with one as it loaded. A visible jump, on exactly the pages that feature exists to keep still.
A translation that arrives as null no longer takes your app down when it starts. A field nobody filled in a content system used to stop everything before the first render. Now that one key is skipped, the app runs, and the console tells you which one it was.
The commands survive a file they cannot read. One file with a syntax error used to end the whole run with a position and no file name. Now the file is named, its texts are skipped, and every other file is still read.
Text inside JSX written in a .js file is found like anywhere else. A React app with components in .js could not run the extract command at all, because the first tag ended it.
A warning no longer repeats itself because a number changed. Three of them printed the value that caused them, so a counter going up could fill memory with copies of the same message.

Full release notesEvery bullet, per package, in the repo changelog.

0.33.0

Release2026-07-29

The public API becomes a decision

The compiler package let you import 132 different things, and not one of them was written down anywhere. They had piled up as whatever the framework packages happened to need, and at version 1.0 every single one would have become a promise nobody had ever reviewed. This version reads the whole list against a written rule, publishes the 60 that survive it, documents them, and adds a test that fails if the list ever grows by accident.

Highlights

If you use the command line or any of the framework packages, this release changes nothing for you. No config, no imports, nothing to edit. Everything here happens inside a package that only custom integrations reach into.
The compiler package now documents what you are allowed to import, in two groups: the types your own config file and your own translation provider need, and the toolkit for building an integration we do not ship. Everything else is internal and now says so.
The list went from 132 names to 60. Each one stayed because a real integration uses it, because it is a documented way to extend Verbaly, or because another one needs it. The 72 that matched none of those are gone.
A build plugin no longer receives the internal parse tree Verbaly reads your code with. It used to get the whole thing just to read two fields off it, and now it gets the messages it found. One less thing that can break when the parser changes.
Both packages fail their own test if the list grows, so adding something public is now a deliberate choice someone reviews, instead of something that happens on the way to fixing something else.

Full release notesEvery bullet, per package, in the repo changelog.

0.32.0

Release2026-07-29

Nothing breaks in silence

Verbaly already refused to build when a translation could not render what your source renders. This version closes the same story from the other end: every remaining place where Verbaly quietly did the safe thing now tells you, at the moment you can act on it. A plural that renders an empty line, a price with no currency, a block written where it cannot work, and a name imported from somewhere it does not exist: four ways to ship the wrong text with everything green.

Highlights

A plural without a catch-all case now warns in the browser, not only in the build. The build check already refused it, but a catalog that arrives from a lazy load or from a content system never goes through the build, so the empty line could still reach a real page. Now it names the message and tells you what to add.
A placeholder missing its argument stops rendering as a bare number. A price with no currency code, a measure with no unit, a date with no time unit: each one used to print the plain value and say nothing. Each one now says what it needs and shows the shape of the fix.
Writing a plural inside a t template no longer ships with the braces visible. In that template the values come from your code, so a plural or a format written there becomes text your users see. verbaly extract and verbaly doctor now point at the file and the exact text.
Importing t from the package finally gets an answer that mentions Verbaly. t comes from your instance or from the generated module, never from the package, and until now only the bundler complained, in a message that gave no hint where t should come from.
Every error from the command line prints its name once. Every failure used to read [verbaly] [verbaly].

Full release notesEvery bullet, per package, in the repo changelog.

0.31.0

Release2026-07-28

The tooling stops contradicting itself

One command called a project healthy while another blocked its build over the same files. The doctor rejected catalogs written as nested groups, even though the runtime has always read them, and told an Astro or Nuxt app to install the package the setup command had just told it not to. The build gate read any word in angle brackets as markup and failed correct translations over it. All of that is now one story: what a command tells you is what your project is.

Highlights

verbaly doctor stops disagreeing with verbaly check. A translation that is there but broken is now an error in the doctor too, so the command you run when something looks wrong can no longer answer "setup looks healthy" about a project whose build fails.
Catalogs written as nested groups work everywhere. The doctor used to reject them as invalid, and the gate only compared the group names, so a group with one untranslated line inside counted as fully translated. Now every line is checked on its own, the way the runtime already read it.
The doctor points at the package your project actually needs: Astro, Nuxt, Next.js, SvelteKit, Vite or the bundler plugin. It is the same answer verbaly init gives, because both now read one table.
The build stops failing over text that only looks like markup. "Press <Enter> to continue" translated as "Pulsa <Intro> para continuar" was reported as two broken tags. A tag counts as structure only when the message closes it, so your prose stays prose and a real emphasis tag or a link is still protected.
Each failure names the step that repairs it, instead of one "run extract" that only ever fixed missing translations. And turning off the missing check now means what it says: you can build with untranslated text, and Verbaly still refuses to ship a translation that renders wrong.
A missing value says which message it came from. The warning used to print the placeholder name alone, once per name, so the second message with the same gap stayed silent.

Full release notesEvery bullet, per package, in the repo changelog.

0.30.0

Release2026-07-28

The build gate stops trusting a filled-in translation

Until now the check asked one question: is there a value for every key? A translation could drop your name placeholder, lose an emphasis tag or flatten a plural block, and the build stayed green while production quietly showed the wrong text, or nothing at all. Now the gate reads every translation against its source and fails on anything that cannot render it, with the reason in plain words and the source line to click. The runtime stops being silent about the same kind of bug, and the React package is verified against Preact.

Highlights

The build now catches translations that are there but broken. A missing placeholder, a lost tag, a plural block turned into plain text, or a plural set with no catch-all case: each one stops the build with a sentence saying what happened and why it matters. Before this, a catalog you edited by hand had no check at all.
The empty-text bug is gone. A plural block that lost its catch-all case rendered nothing at all for every count it did not list. In Polish, a message with only "one" and "few" showed an empty string for 5 items. That fails the build now instead of shipping.
Verbaly tells a translator which plural forms their language actually needs. A Polish or Russian catalog carrying only two forms gets a warning naming the missing ones. It is advice, not a failure: the text still renders. Forms no real counter ever reaches are never asked for, so Spanish, French, Portuguese and Italian stay quiet.
verbaly status shows a broken count per language, so you can see the state of a catalog without running the gate.
A missing value now warns in the console. Rendering a raw placeholder because nobody passed the value was the one bad-data case Verbaly did not report. Every other one already did.
Preact works, and now it is proven. The React package runs its whole suite a second time with React resolved to preact/compat: hooks, language switching, rich text and server rendering all pass. No separate package, no changes to your code.
VS Code can show your translations on hover. The repository README carries the i18n-ally setup that turns hashed keys into readable text while you code.

Full release notesEvery bullet, per package, in the repo changelog.

0.29.0

Release2026-07-27

Your coding agent can now run the whole translation cycle

A new MCP server gives Claude Code, Cursor and any MCP client four tools: see the coverage, list what is missing, extract new text and machine-translate the gaps. Everything the agent translates still waits for your review. A public Agent Skill and an llms.txt on the docs complete the channel, Nuxt projects keep their root clean, and displayed code snippets can no longer become phantom keys.

Highlights

The translation cycle as agent tools. One command (claude mcp add verbaly -- npx -y @verbaly/mcp) and your coding agent can check coverage, list missing translations, extract new text and fill the gaps with machine translation. Anything it translates is saved as a draft, so nothing ships without a human saying yes.
A public Agent Skill teaches your agent Verbaly. Install skills/verbaly from the repository into your project and the agent knows the write, extract, check, translate cycle and the rules that keep it safe.
The docs now speak LLM. This site publishes an llms.txt index, so agents that read documentation find their way around Verbaly without scraping HTML.
Nuxt projects keep their root clean. The generated types now live inside .nuxt/ and register themselves, exactly like the Astro integration already did. No file at the project root and no tsconfig edits.
Displayed code can no longer become a translation key. Pages that show t examples as visible text in Vue, Astro or Svelte files used to risk those snippets being extracted as real keys. Now only code inside real expressions counts.

Full release notesEvery bullet, per package, in the repo changelog.

0.28.0

Release2026-07-20

Gettext PO, protected placeholders and a sturdier runtime

The translator toolkit is now complete: export and import gettext PO files, and XLIFF now protects your placeholders and tags so a translator cannot break them by accident. A custom sitemap name in render finally works, a rare crash with invalid dates is gone, and the runtime cannot silently grow past its size budget.

Highlights

Export and import gettext PO files. verbaly export --format po writes one .po file per language, ready for Poedit, Weblate or any PO editor. verbaly import reads them back with the same safety net as every other format: a translation that breaks a placeholder is rejected, not shipped. Entries a tool marks as fuzzy count as untranslated.
Translators can no longer break your placeholders in XLIFF. Placeholders and tags travel as protected codes with meaningful names, so translation tools show them as untouchable chips instead of editable text. Plural and select words stay editable on purpose: those need translating.
Custom sitemap names work now. Setting a custom filename for the sitemap in render used to be ignored: it always wrote sitemap-i18n.xml. The name you configure is the name you get.
A rare crash is gone. Passing an invalid date to a message could throw instead of degrading gracefully. It was found by a new randomized test suite that hammers the parser with garbage on every run, so this class of bug stays fixed.
The runtime cannot silently grow. Every push now measures the core bundle and fails if it exceeds its size budget. The ~3 KB promise is enforced by a machine, not a habit.

Full release notesEvery bullet, per package, in the repo changelog.

0.27.0

Release2026-07-19

Machine translations you review before trusting

Machine translations now arrive as drafts you review, not as finished work you trust blindly. A new review command approves them, the CI gate can wait for a human, and the model translates with context from your code.

Highlights

Machine output is a draft until you say otherwise. verbaly translate still fills the gaps, but every text it writes is now flagged as an unreviewed draft. Your catalogs stay exactly as clean as before: the review state lives in a separate .verbaly-drafts.json file next to them.
Approve translations when you have read them. verbaly review lists everything waiting for a human; verbaly review --approve accepts it, all of it or one locale at a time. Importing a translator's file counts as review too, so the draft flag clears on its own.
Block merges on unreviewed machine text. verbaly check --drafts fails CI while any machine translation is still unreviewed. Plain verbaly check is unchanged, so nothing breaks until you opt in.
Better translations, because the model gets context. verbaly translate now tells the provider which source files each text appears in, so tone and length fit where the text is used.
See what needs review at a glance. verbaly status (and --json) now report the count of unreviewed drafts per language.

Full release notesEvery bullet, per package, in the repo changelog.

0.26.0

Release2026-07-18

Astro support, a wrap codemod and CI annotations

Astro joins the family: one line wires everything and the per-locale rendering runs by itself. A new wrap command wraps your hardcoded JSX text for you, and CI failures become annotations right on your pull requests.

Highlights

Astro support, one line. Add verbaly() to the integrations in astro.config and everything is wired: live extraction while you code, type-safe keys and the build gate. The typed keys live inside Astro's own .astro folder, so no extra file lands in your project. In the mirror flow, verbaly render runs by itself after every build.
Write your text right in .astro files. The same t`…` you already use in .js, .tsx, .svelte and .vue now works in the frontmatter and the markup of Astro components.
Migrating an existing app? Let verbaly wrap do the boring part. It scans your JSX, finds the hardcoded user-visible text and wraps it in t`…` for you. It reports first; nothing is touched until you pass --write.
CI failures now point at your code. verbaly check --reporter github turns every missing translation into an annotation on the exact file and line, right on the pull request.
verbaly status --json gives you the coverage numbers machine-readable, ready for badges and dashboards.

Full release notesEvery bullet, per package, in the repo changelog.

0.25.0

Release2026-07-18

Automatic RTL, real language names and context for translators

Adding Arabic or Hebrew now just works: the page direction follows the language everywhere. Language switchers get real names from the platform, and translator files say where each text lives.

Highlights

Right-to-left languages just work now. Add Arabic, Hebrew or Persian and the page direction follows the language on its own: when the user switches, when the server renders, and in pre-rendered static pages. No dir attribute to manage, ever.
Language switchers without hardcoded names. localeName('es') returns 'español' and localeName('de', 'en') returns 'German'. The names come from the platform, so any locale works without maintaining a table.
Need the direction yourself? localeDirection('ar') returns rtl. It is the same helper the rest of the toolkit uses, exported for your own layouts.
Translators now see where each text lives. verbaly export marks every message with the source files it came from: XLIFF gets standard location notes and CSV gets a location column, so context stops being guesswork.

Full release notesEvery bullet, per package, in the repo changelog.

0.24.0

Release2026-07-16

Literal braces and safer pre-rendered pages

Rich messages can finally show a literal brace, and pages pre-rendered with verbaly render now apply the same security rules as the browser.

Highlights

Messages can now show literal curly braces. Write { and } in a rich message and they render as { and }. Hex forms like { work too, in the browser, in every <Trans> and in pre-rendered pages.
Pre-rendered pages are now as safe as the browser. Translated attributes go through the same guards, so unsafe links and dangerous attributes from a catalog never reach the static HTML.

Full release notesEvery bullet, per package, in the repo changelog.

0.23.0

Release2026-07-14

One <Trans> everywhere, live extraction and a coverage view

The React, Vue and Svelte <Trans> components now share the same props and the same rendering rules, the CLI learns two everyday commands, and the last planned breaking changes land before 1.0.

Highlights

<Trans> is now the same component in React, Vue and Svelte: same props, same rendering rules. Your custom component wins, then named links, then the safe tag whitelist; anything unknown degrades to plain text.
Breaking: React and Vue <Trans> now render whitelisted tags like em and code as real elements, matching Svelte and the DOM interpreter. Pass an empty richTags list to keep the old flatten-to-text behavior.
Breaking: @verbaly/svelte now requires Svelte 5. In exchange <Trans> gains the components prop: map a tag in a message to your own component. On Svelte 4, stay on 0.22.0.
verbaly status shows how much is left to translate, one line per language, without failing anything. verbaly check stays the build gate.
verbaly extract --watch keeps catalogs and types in sync as you code, made for webpack, Rspack and Rollup setups where the Vite plugin is not available.
Easier to give feedback: the README points bug reports and friction reports to the right place, and the issue forms cover all ten packages.

Full release notesEvery bullet, per package, in the repo changelog.

0.22.0

Release2026-07-14

Your catalogs become native mobile resources

The export command learns two mobile formats: Android resource folders and iOS string files. A web app and its mobile companion can now share one set of translations.

Highlights

Export your translations for mobile apps: verbaly export --format android-xml writes folders you can drop into res/, and --format ios-strings writes .lproj folders for Xcode.
Sensible defaults for each platform: your source language becomes the platform default, and untranslated keys are left out so the app falls back to it instead of showing empty text.
Safer catalog files: a catalog with broken JSON now stops the command and names the file, instead of being silently read as empty. A Windows BOM at the start of the file is simply tolerated.

Full release notesEvery bullet, per package, in the repo changelog.

0.21.0

Release2026-07-14

A quality pass, and typed Nuxt config

A cleanup sweep across all ten packages, plus fully typed options in your Nuxt config. The internals got tidier and a little smaller, with no change to how you write Verbaly.

Highlights

The verbaly key in nuxt.config.ts is now fully typed: you get autocomplete and typo checking, and the module still adds no extra dependency.
A calmer editor in dev. verbaly.d.ts is only rewritten when its contents actually change, so your TypeScript server stops reloading types on every save.
A slightly smaller runtime: the tree-shaken core is now 3.28 KB gzipped, down from 3.30.
Cleaner generated types: a value used as both a date and plain text no longer shows up twice in verbaly.d.ts.
Clearer command-line messages. Every error and hint reads in plain words, and check now prints the source text right next to the missing key.

Full release notesEvery bullet, per package, in the repo changelog.

0.20.0

Release2026-07-13

Write your text in .svelte and .vue files too

Natural text now works inside Svelte and Vue components: write it in the file, script or markup, and the compiler extracts it with a stable key and typed params.

Highlights

Write t`Hello ${name}` directly in a .vue template or {$t`Hello ${name}`} in .svelte markup. The compiler picks it up like it always did in .ts files: stable key, typed params, per-locale catalogs.
Svelte's store form is understood: $t`…`, $t('key') and $t.id('key')`…` all work anywhere in a .svelte file.
Live in dev, gated in build: save a component with new text and the catalogs plus verbaly.d.ts update on the spot. Missing translations still stop the build.
Readable keys and runtime keys work in markup too: t.id('home.title')`…` extracts under your key, and t('key') calls count as used keys for check and prune.
verbaly extract scans more by default: .svelte and .vue files, plus the app/ folder next to src/ (where Nuxt 4 and the Next.js App Router live). Your own include config still wins.

Full release notesEvery bullet, per package, in the repo changelog.

0.19.0

Release2026-07-13

Next.js joins the family: the cycle is complete

The last big meta-framework integration. Next.js App Router pages render already translated, hydrate without a flash, and work on both Turbopack and webpack.

Highlights

New package @verbaly/next. Two steps: wrap your config with withVerbaly() in next.config.ts and drop <VerbalyProvider> into the root layout. Server Components translate with await getT(); Client Components keep using useT and <Trans> as in any React app.
Works on Turbopack (the Next 16 default) and on webpack. next dev extracts your messages as you type, and next build stops if a translation is missing.
Every visitor gets their own language, resolved once per request from their cookie or browser preferences. Pages arrive already translated, nothing flashes, and concurrent visitors never see each other’s language.
useSwitchLocale() changes the language instantly, remembers the choice for the next visit, and updates Server Components too.
Rich messages can now display literal markup, so a message can show "<html lang>" as visible text instead of a broken escape.

Full release notesEvery bullet, per package, in the repo changelog.

0.18.0

Release2026-07-13

Nuxt joins the family

The second meta-framework integration: a zero-config Nuxt module renders every page in the visitor’s language and hydrates without a flash.

Highlights

New package @verbaly/nuxt. One line in your config (modules: ['@verbaly/nuxt']) wires everything: live extraction, per-visitor language, and hydration with the same locale and catalog the server used. No flash, no mismatch.
No framework lock: the module depends on neither nuxt nor @nuxt/kit, and it is verified against a real Nuxt 4 app.
switchLocale() is now a core export shared by SvelteKit, Nuxt and hand-rolled setups. It loads the catalog first and switches after, so nothing flashes. Existing imports keep working.
Client-only apps are covered too: with ssr: false the module still picks the right language in the browser.
Support Verbaly: GitHub Sponsors is live at github.com/sponsors/AronSoto.

Full release notesEvery bullet, per package, in the repo changelog.

0.17.0

Release2026-07-11

Robust inside, for real

The hardening release: a full audit of all eight packages fixed every sharp edge it found, and SSR gets its missing piece.

Highlights

Attribute translation is now XSS-safe end to end: data-verbaly-attr sanitizes URL attributes and blocks style and srcdoc entirely, so a compromised catalog can’t inject scripts.
t() never crashes on bad format arguments: an invalid currency code, date or time style warns once and renders the plain value.
createRequestInstance(locale) in virtual:verbaly: the SSR per-request pattern in one call, with the catalog already loaded and no flash.
The CLI now rejects misplaced flags. verbaly translate --locale es used to silently translate all locales; now it errors and suggests --locales. Plus --dry-run for extract --prune.
normalizeLink() and resolveRequestLocale() now live once in core, shared by every adapter and SSR integration.
Breaking: instance.inspect(key) now returns { from, source } instead of { locale, source }: one name for one concept across the observability API.

Full release notesEvery bullet, per package, in the repo changelog.

0.16.0

Release2026-07-11

Server-side rendering, for real

The first meta-framework integration: SvelteKit pages render in the visitor’s language on the server and hydrate without a flash.

Highlights

New package @verbaly/sveltekit. SSR in three wires: verbalyHandle() in your server hooks, one +layout load, and %verbaly.lang% in app.html. Pages arrive translated.
The language is decided per request: cookie first, then the Accept-Language header (es-PE matches es), then your fallback. Concurrent requests never leak each other’s language.
switchLocale(): a client-side switch that loads the catalog first, then saves the choice in the cookie the server reads.
negotiateLocale() in core: the Accept-Language matcher is a public export any Node server can use.
createInstance() in virtual:verbaly: fresh request-scoped instances over your compiled catalogs, plus locales and sourceLocale exports.

Full release notesEvery bullet, per package, in the repo changelog.

0.15.0

Release2026-07-10

Your translators can work now

The write→ship cycle opens up to humans: export translator-ready files, import them back validated.

Highlights

verbaly export writes one translator-ready file per locale: XLIFF 2.0 for translation platforms, CSV for spreadsheets. --missing exports only what’s left to translate.
verbaly import validates every entry: a translation that drops a placeholder, a variant or a tag is rejected and reported.
Existing translations are kept unless you pass --overwrite, and --dry-run previews the whole import.
No translation platform needed: catalogs are plain JSON, and Crowdin, Lokalise and Phrase read it natively.

Full release notesEvery bullet, per package, in the repo changelog.

0.14.5

Release2026-07-10

Revision of 0.14.0: the review release

A hard audit of what 0.14.0 shipped found three real defects. All fixed here.

Highlights

The verbaly/devtools overlay no longer freezes the page: its observer now ignores its own writes.
"" now means untranslated everywhere: the runtime falls back instead of rendering a blank hole.
Locale mirrors get self-canonical rel="canonical" and og:url, so the hreflang set finally counts.

Full release notesEvery bullet, per package, in the repo changelog.

0.14.0

Release2026-07-10

Ships translated, and you can see why

Multi-locale SEO for the static renderer, runtime observability, hardened server-side use.

Highlights

verbaly render emits reciprocal hreflang alternates and an i18n sitemap: set render.baseUrl and go.
Opt-in verbaly/devtools: hover any element to see its key, status and source locale.
New onResolve hook + inspect(key), with zero cost when unused.
Server-side Node use hardened and locked with tests.

Full release notesEvery bullet, per package, in the repo changelog.

0.13.1

Release2026-07-10

README refresh: readable on npm dark mode

Docs-only patch; first release published from CI with npm provenance.

Highlights

The seven package READMEs are readable on npm’s dark theme and friendlier to skim.
MIT re-affirmed; releases now ship with npm provenance from the automatic workflow.

Full release notesEvery bullet, per package, in the repo changelog.

0.13.0

Release2026-07-09

verbaly doctor + adoption & trust

One command answers “why isn’t this translating?”, and a real path off i18next.

Highlights

verbaly doctor inspects config, catalogs, plugin wiring, stale types and orphan keys, and gives each finding its exact fix.
New Migrate from i18next guide: keep your keys and JSON, swap the runtime page by page.
Publishing moves to GitHub Actions with npm provenance: every package is publicly linked to its commit.

Full release notesEvery bullet, per package, in the repo changelog.

0.12.0

Release2026-07-09

verbaly init + the TypeScript 7 toolchain

From zero to translating in one command; the build moves to tsdown and native TS 7.

Highlights

verbaly init scaffolds config + catalogs and detects your bundler. It never overwrites.
Toolchain: tsup → tsdown; typecheck on native TypeScript 7 (~10× faster). No consumer-visible change.

Full release notesEvery bullet, per package, in the repo changelog.

0.11.0

Release2026-07-08

Rich links + the full modern Intl surface

Named links with hrefs that never come from catalogs, and the last missing Intl formatters.

Highlights

Named links in rich messages render real <a> elements. The href comes from your code, never the catalog, and unsafe schemes are blocked.
Relative time ({when:relative}), lists ({xs:list}) and CLDR units ({n:unit/kilometer}): all native Intl, zero dependencies.
License: Apache-2.0 → MIT across all seven packages.

Full release notesEvery bullet, per package, in the repo changelog.

0.10.0

Release2026-07-07

Static sites ship translated + Verbaly beyond Vite

The FOUC dies on SSG, and webpack/Rollup/esbuild/Rspack join via unplugin.

Highlights

verbaly render pre-fills your built HTML per locale with the real runtime, so static pages ship already translated.
New @verbaly/unplugin: the same virtual modules + build gate on webpack 5, Rollup, esbuild and Rspack.
verbaly pseudo: a QA locale (⟦Ĥéĺĺó ~⟧) that exposes hardcoded strings and clipped layouts.
<Trans> lands in Svelte.

Full release notesEvery bullet, per package, in the repo changelog.

0.9.0

Release2026-07-06

Machine translation closes the loop

write → extract → translate → check green: the whole cycle in one tool.

Highlights

verbaly translate fills the "" holes check reports: batched, with --dry-run and per-locale filters.
Structural validation: placeholders, variants and tags must survive verbatim or the translation is rejected.
Pluggable providers: Claude as the reference, and any (messages) => translations function works. Zero runtime impact.

Full release notesEvery bullet, per package, in the repo changelog.

0.8.0

Release2026-07-06

Readable keys + lazy catalogs

Human-readable ids when you want them, per-locale lazy loading when you need it.

Highlights

t.id('inbox.title')`Hello ${name}`: readable, namespaced keys; hashed stays the zero-config default.
loaders in createVerbaly: bundle only the source locale and load the rest on demand, flash-free with await loadLocale.

Full release notesEvery bullet, per package, in the repo changelog.

0.7.0

Release2026-07-04

Svelte joins the ecosystem

Idiomatic stores over the same reactive core, for Svelte 4 & 5.

Highlights

@verbaly/svelte: $t('key') re-renders on locale switch, and bind:value={$locale} just works.
Context via provideVerbaly/useVerbaly or store factories without a component tree.

Full release notesEvery bullet, per package, in the repo changelog.

0.6.0

Release2026-07-04

The compiler understands your whole codebase

Write JSX in place and the compiler extracts it.

Highlights

<Trans> write-in-place extraction: source text with real elements becomes key + components automatically.
verbaly.config.ts / .mts support (esbuild as optional peer).

Full release notesEvery bullet, per package, in the repo changelog.

0.5.0

Release2026-07-04

Hardening + performance, with receipts

Benchmarks vs i18next run on every release from here on.

Highlights

Hot path memoized end to end: lookup 31×, interpolation 10×, plurals 5× vs i18next.
Defensibility audit: cached fallback chains, per-element DOM args, capped AST cache.

Full release notesEvery bullet, per package, in the repo changelog.

0.4.0

Release2026-07-04

The DOM interpreter catches up

Rich text in plain HTML, safely, plus locale bootstrap helpers.

Highlights

data-verbaly-rich: tagged messages render real elements from a phrasing whitelist, never innerHTML.
resolveLocale / persistLocale: storage → navigator → fallback, SSR-safe.

Full release notesEvery bullet, per package, in the repo changelog.

0.3.0

Release2026-07-03

ICU escape-hatch + robustness

Bring your ICU strings: auto-detected, zero dependencies.

Highlights

ICU MessageFormat (plural, select, selectordinal) parses into the same engine, opt-in per message.
Hardened <Trans> tokenizer + build-time key-collision warnings.

Full release notesEvery bullet, per package, in the repo changelog.

0.2.0

Release2026-07-03

Ecosystem public + rich text

First npm publish of the ecosystem packages.

Highlights

@verbaly/compiler, @verbaly/vite, @verbaly/react and @verbaly/vue land on npm, version-aligned.
<Trans> in React and Vue: interpolate elements inside translated sentences with named tags.

Full release notesEvery bullet, per package, in the repo changelog.

0.1.0

Release2026-07-02

The first release

The core idea, working: write text, ship translations.

Highlights

Runtime: message format over native Intl, reactive locale store, DOM interpreter, type-level keys and params.
Compiler: AST extraction of t`…` into stable hashed keys, extract/check, typed verbaly.d.ts.
Vite plugin: live extraction, HMR, per-locale code-splitting, builds fail on missing translations.

Full release notesEvery bullet, per package, in the repo changelog.