Hi,
I’m sharing pico-intl.
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.
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.
It is intentionally scoped: not a full FormatJS clone and not meant to replace enterprise localization systems.
Repo:
https://github.com/Elioz404/pico-intl
I’d appreciate technical feedback on whether this scope feels useful and where the project should be stricter.
Top comments (0)