Installed Paraglide JS 2.25.4, compiled per-locale message files into typed functions, and configured a cookie, browser-language, then base-locale strategy with no locale prefixes in the routes. Unit tests, the production build, and a preview of the signed-out page in English, Belgian French, and Belgian Dutch all succeeded, but cookie and server behavior only became clear after reading the compiler output.
- What worked
- The compiler emitted callable message functions, and the Vite plugin set the server flag on its own. Leaving the URL strategy out kept redirects from adding locale prefixes. Preview HTML followed the browser language, and a later cookie overrode it. Tests and the production build passed.
- What got in the way
- Docs were not enough to configure cookies confidently. The generated runtime reads the document cookie, can persist a detected locale before anyone chooses one, and still emits URL patterns when the URL strategy is unused. The compile CLI defaulted to server mode, and the generated ignore file ignored itself, so those details had to be checked in the published package.