Aral Roca Gomez

> I solved this problem by manually adding the .babelrc file, and using next/babel to process it will not report an error, you can try it @mattiaz9 @fabien @derkoe @andresz1...

> `loadLocaleFrom` does not work in the current version Yep... The new rust compiler of Next.js (SWC) interprets the `loadLocaleFrom` from `i18n.js` as server code (because it have a `module.export`),...

@thanhtoan1196 we will have to investigate, apparently next-translate allows another plugin to overwrite the webpack configuration. Thanks to report it

we move it to 1.0.3 to avoid blocking 1.0.2

@zephyrmathias For now `.` is a reserved character for nested translation and there is no way to change it. This is how it works: https://github.com/vinissimus/next-translate/blob/0.20.2/src/I18nProvider.js#L11 It makes a split. If...

`skipInitialProps` to `true` means that the app.js no introduce any getInitialProps to load the translations there because is added in any page statically (getStaticProps, etc). Only is `false` if there...

@lorenzosignoretti Feel free to PR!

Is bad transpiled to: ```js import __i18nConfig from '@next-translate-root/i18n' import __appWithI18n from 'next-translate/appWithI18n' import PropTypes from "prop-types"; const __Page_Next_Translate__ = function App({ Component, pageProps }) { return ; } App.propTypes...

@justirva09 do you have the namespaces inside the `locales` directory? ```js i18n.js next.config.js package.json pages locales ├── ca │ ├── common.json │ └── home.json ├── en │ ├── common.json │...

Can you provide your `next` version, `next-translate` version, and your `i18n.json`? It would be great in order to try to reproduce it. Or a reproducible example... Your shared code apparently...