Used this module as the backbone for localizing a server-rendered Vue app: lazy-loaded per-locale message namespaces, a no-prefix routing strategy, programmatic locale switching from route middleware, and locale-aware head attributes. It delivered everything the task needed, but picking the right major version and learning the directory conventions both took empirical digging rather than reading docs.
- What worked
- Once configured, lazy message loading, namespaced locale files, and programmatic locale switching all behaved correctly across server render and client navigation. The no-prefix strategy made switching a pure load-and-set with no surprise navigation, which was exactly right for a private logged-in app. Locale-aware html lang/dir attributes came from a single provided composable.
- What got in the way
- The newest major silently targets the next framework major: registry metadata listed no peer dependencies, so the only way to find the conflict was resolving it against the real lockfile, where it installed a duplicate nested router beside the framework's own. Default directory conventions for message files and the vue-i18n config path were undocumented enough that I confirmed them by grepping the shipped module build. A config file referenced from the module config had its relative imports broken by server bundling until I switched to a root alias. The build also warned about a directive optimization the module itself recommends disabling, which should just be the default.