The latest articles on DEV Community by Elioz404 (@elioz_404). https://dev.to/elioz_404 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3934139%2F10b54591-bdb6-4693-a122-283b377783ae.png https://dev.to/elioz_404 en Elioz404 Sat, 16 May 2026 03:15:52 +0000 https://dev.to/elioz_404/typescript-first-i18n-toolkit-with-cli-workflows-and-tested-adapters-for-react-next-vue-svelte-20nb https://dev.to/elioz_404/typescript-first-i18n-toolkit-with-cli-workflows-and-tested-adapters-for-react-next-vue-svelte-20nb <p>Hi,</p> <p>I’m sharing pico-intl.</p> <p>The idea is to focus less on runtime claims and more on the workflow around JSON-based localization: extraction, validation, placeholder checks, generated TypeScript types, import/export, and CI gates.</p> <p>It also has opt-in adapters for React, Next.js, Vue, Svelte, Solid, Astro, and Angular. Recently I added a shared adapter contract test suite so “framework agnostic” means consistent observable behavior across adapters, not pretending every framework has the same rendering model.</p> <p>It is intentionally scoped: not a full FormatJS clone and not meant to replace enterprise localization systems.</p> <p>Repo:<br> <a href="https://github.com/Elioz404/pico-intl" rel="noopener noreferrer">https://github.com/Elioz404/pico-intl</a></p> <p>I’d appreciate technical feedback on whether this scope feels useful and where the project should be stricter.</p> showdev tooling typescript webdev