Aral Roca Gomez
Aral Roca Gomez
I believe this issue has been resolved with Next-translate 2.0, as we have rewritten the plugin and replaced the use of regex with a parser. This update has automatically addressed...
I believe this issue has been resolved with Next-translate 2.0, as we have rewritten the plugin and replaced the use of regex with a parser. This update has automatically addressed...
@TechnologicNick feel free to PR
To do that you can turn off the Webpack plugin and use the [`I18nProvider`](https://github.com/aralroca/next-translate#i18nprovider) and manage the locale state by yourself. i18n.js ```js module.exports = { ...restOfI18nConfig, loader: false }...
Formatters are already supported in next-translate new versions: https://github.com/aralroca/next-translate#9-formatter
I'm not sure how we can solve the revalidate problem from our side, it's something internal to Next.js core. Any idea feel free to PR
Should be fixed in `2.0.0-canary.3` 👍
I'm going to close the issue because is not possible to reproduce it with this info. Next-translate with Node 16 is working fine.
Yes, we are going to priorize this. However feel free to PR 👍😊
Feel free to PR improving the types