Framework Adapters
Framework Adapter Contract
The framework-agnostic promise is precise: one translation model, one catalog/config workflow, and one tested behavioral contract across adapters.
ts
npm run test:adapter-contract
# Covered semantics:
# translation, fallback, exists(), locale reads,
# locale switching where supported, dir, and isRTL.Key points
- Adapters share translation, fallback, exists(), locale reads, and LTR/RTL metadata semantics.
- Framework-specific behavior such as routing, SSR, hydration, stores, signals, and dependency injection remains explicit.
- npm run test:adapter-contract is wired into local verification, CI, coverage release checks, and release publishing.
Next step
Copy the example into a small fixture, run the validation commands, and keep framework-specific routing, hydration, or SSR behavior covered by your app tests.