Aral Roca Gomez

@wilsonneto-dev thanks so much to share your code. This was very useful, it helped us too much! We found a bug when the `_app.js` don't have a `getInitialProps`. This will...

@rriski is it already happening to you on [1.0.2-canary.2](https://github.com/vinissimus/next-translate/releases/tag/1.0.2-canary.2) prerelease? If it still happens to you, can you share more details about your problem? if you have a reproducible example...

Thanks to report it @rriski

Have you tried this? ```js const MarketPage = connect(mapStateToProps)(Market) MarketPage.getInitialProps = getInitialProps export default MarketPage; ``` Instead of: ```js Market.getInitialProps = getInitialProps export default connect(mapStateToProps)(Market); ``` I don't know if...

the first comment on the issue was before 1.0 and we reimplemented everything to support the i18n routing of Next.js, but I see that in +1.0 it is not fixed...

All Next-translate does is pass the configuration you pass to Next.js. It doesn't touch anything... Line 50, defined on line 3 https://github.com/vinissimus/next-translate/blob/49f580c6d292712a0720a104de3b487e7c11d4ae/src/plugin/index.ts#L49-L56 The whole i18n routing also uses the Next.js...

1.0.0-experimental.4 is quite old. Can you try 1.0.0-canary.2? which is the last prerelease. Not sure if exist this type but we increased the types. If it's definitely not there either,...

Also the `useTranslation` export exists https://www.runpkg.com/[email protected]/useTranslation/package.json ... > How do you build the lib folder the following fields in package.json are referencing to Just doing `yarn build` and it executes...

what is rare is that the repo examples use the canary.2 version with esm and it works well...! Maybe it would help if you create an example reproducing the error🙏

It is likely that by migrating the project to TypeScript in version 1.0 some types have changed, some improved, but others may need to be re-added. > I did upgrade...