Release v0.26.0
Astro joins the family, and adopting Verbaly on an existing app stops being a chore. A new @verbaly/astro integration wires everything with one line and runs the per-locale rendering by itself; the compiler now extracts text written directly in .astro files; a new verbaly wrap command finds your hardcoded JSX text and wraps it for you; and verbaly check can now report failures as clickable annotations on your GitHub pull requests. No breaking changes.
Highlights
- Astro support, one line. Add
verbaly()to the integrations inastro.configand everything is wired: live extraction while you code, type-safe keys, and the build gate. The typed keys live inside Astro's own.astrofolder, so no extra file lands in your project. If you use the pre-translated mirror flow,verbaly rendernow runs by itself after every build. - Write your text right in
.astrofiles. The samet`…`you already use in.js,.tsx,.svelteand.vuenow works in the frontmatter and in the markup of Astro components. The compiler extracts it, types it, and keeps the catalogs in sync. - Migrating an existing app? Let
verbaly wrapdo the boring part. It scans your React (or any JSX) code, finds the hardcoded user-visible text, and wraps it int`…`for you. It reports first; nothing is touched until you pass--write. Anything ambiguous is listed for a human instead of guessed. - CI failures now point at your code.
verbaly check --reporter githubturns every missing translation into a GitHub annotation on the exact file and line where the text lives, right on the pull request. verbaly status --jsongives you the coverage numbers machine-readable, ready for badges and dashboards.
For the full details of this release, see the repository changelog.