Aral Roca Gomez

I would like to understand in which cases you need `shallow=true`? Shallow routing allows you to change the URL without running data fetching methods again, which includes getServerSideProps, getStaticProps, and...

@Aeet Maybe you can use a hook using the `getT` function to download in client-side the necessary translations without doing it in the fetching methods. I guess it would be...

I don't know if there is a way to know if the current navigation comes from shallow routing, if so, maybe we could force the `I18nProvider` to download the necessary...

@tperamaki The source code is not included on >1.0 (neither in development). Here is the package of 1.0.1: https://www.runpkg.com/[email protected] Witch version of next-translate do you have? 🤔

@tperamaki Sorry for the misunderstanding. Now I understand what you are saying. We are reading directly in pages to know if the _app.js has a getInitialProps or not. - https://github.com/vinissimus/next-translate/blob/1.0.1/src/plugin/index.ts#L55-L61...

Perhaps we can use the loader to check once all the resources that ends with app.js, ts, jsx... I note this as an issue for 1.0.2. Thanks to report it...

we move it to 1.0.3 to avoid blocking 1.0.2

any contribution is welcome

Instead of: ```js const nextTranslate = require('next-translate') module.exports = { webpack: (config, { isServer, webpack }) => { return config; }, ...nextTranslate() } ``` Try: ```js const nextTranslate = require('next-translate')...

@nbouvrette You can load at page level all translations that are visible when rendering, and load dynamic components dynamically with [DynamicNamespaces](https://github.com/vinissimus/next-translate/tree/1.0.6#dynamicnamespaces).