Aral Roca Gomez
Aral Roca Gomez
I mean this: `experience.json`: ```json { "API Restful Javascript com Node.js, Typescript, TypeORM etc": "API Restful Javascript with Node.js, Typescript, TypeORM etc" } ``` Using: ```js t('experience:API Restful Javascript com...
Ah yes. The dot is for nested keys: ```json { "example": { "nested": "bla" } } ``` `t('namespace:example.nested')` You can change `.` key separator usage in the [`keySeparator`](https://github.com/vinissimus/next-translate#3-configuration) configuration
> Use like the code below? >```json > "API Restful Javascript with Node": { > "JS, Typescript, TypeORM etc": "API Restful Javascript with Node.js, Typescript, TypeORM etc" > }, >```...
Do you need the last version [1.3](https://github.com/vinissimus/next-translate/releases/tag/1.3.0). Update it 😉
Are you doing `next build && next start`? or `next build && next export`? In case of `next export` is an unsupported feature by next-translate (Internationalized Routing ) https://nextjs.org/docs/advanced-features/static-html-export#unsupported-features
replace this: ```js const nextTranslate = require('next-translate'); module.exports = { trailingSlash: true, images: { domains: ['source.unsplash.com'] }, ...nextTranslate() }; ``` to: ```js const nextTranslate = require('next-translate'); module.exports = nextTranslate({ trailingSlash:...
You need to update to the last version of Next.js. Should be fixed after this PR https://github.com/vercel/next.js/pull/21930. Try Next.js 10.2.3 😊
@Gyaniultimate after migrate Next.js solve it?
Would be great if you share a reproducible example 🙏 Thanks
@gsambrotta I think is the same issue reported here: https://github.com/vinissimus/next-translate/issues/395 On the issue there is a workaround proposed to temporal fix this. Hope it helps 😊