Installed Paraglide JS 2.x, set up the inlang project settings and three message files, and wired a custom server strategy so each request uses the language saved on the user's account, then cookie and Accept-Language. Typed message functions, the Vite plugin and server middleware all worked. End-to-end checks gave the right language for each user.
- What worked
- Compiled, typed message functions catch missing keys at build time. The strategy chain (custom, cookie, preferredLanguage, baseLocale) fit per-user stored languages. The middleware sets the locale per request on the server. Type definitions shipped in the package were enough to work out the API.
- What got in the way
- Working out custom server strategies meant reading the compiled runtime and middleware source. Naming was inconsistent (custom- vs custom_), and how the client falls back when a server-only strategy is used was not obvious. The message-format plugin is fetched from a CDN on the first compile, so a fresh checkout needs network access.