Lazy Loading|

Eager registration ships every locale's strings in the initial bundle. That's simplest and right for a handful of languages (en/de). Past that, the inactive locales are dead weight on first paint — register them as dynamic-import loaders so only the active language is in the initial bundle, and the rest load on activation.

Pass options.loaders to createPackageI18n. The bundle in translations (typically en) stays eager as the base/fallback; each listed locale becomes a dynamic import that Vite/Rollup splits into its own chunk.

Compile-time key parity is not checked for lazy locales — the chunk isn't visible to the type-checker. Guard parity at runtime with validatePackageTranslations in a test.

The provider drives loading automatically:

• On mount it loads the active locale and the fallback. (Effects don't run during SSR, so a lazy non-base initial locale renders the fallback on the server and the first client paint, then re-resolves reactively once its chunk lands.)
• On switch, setLocale triggers the target's loader (not awaited) and flips the locale; the $derived reads re-resolve when the chunk arrives.
• If a load fails and no data exists for that locale, load-failed-no-fallback is reported to the error sink — the loud signal that "the language you switched to can't be rendered."

useI18n().isLoading is true while a lazy load is in flight — wire it to a spinner if a switch is perceptible: