Status: Package release coming
Built and tested. Package release coming: not on npm yet.
Add translated pages to nuxt generate
A Nuxt module hooks the end of the static build and writes a translated copy of every generated page under its language folder.
Who it is for
- Teams deploying a Nuxt site with nuxt generate to static hosting.
- Sites that need indexable pages per language without a translation server in production.
- Developers who want translations built and checked in CI.
Honest limits
- Built and tested. Package release coming: the module is not on npm yet.
- It translates static output. With nuxt build and the node-server preset there are no static pages, so nothing is touched. Dev mode is skipped.
- Translated pages are plain HTML by default. In our tests the Nuxt client router did not know the /fr/ folder and navigated out of the language, so hydration is stripped by default.
- Tested against Nuxt 4.5; other versions are not verified.
How it works in 3 steps
Add the module
Add @resilientlang/nuxt to modules and set the source language, site URL, bundle location and public key.
Run nuxt generate
After Nitro finishes prerendering, the module reads your signed bundle (signature mandatory) and translates the finished pages.
Deploy the folder
Each language gets its own folder with lang and dir attributes, reciprocal hreflang with x-default and canonical tags. The output is static files.
Questions
Does it run with nuxt build?
No. It needs static pages, so use nuxt generate. With a node-server build nothing is changed.
Why are translated pages not interactive?
In our tests a hydrated translated page navigated out of its language. Until the router is language-aware, translated copies are plain HTML. Your source-language pages are unchanged.
Is it on npm?
Not yet. It is built and tested; the npm release is still to come.