Aral Roca Gomez
Aral Roca Gomez
@gurkerl83 About the named exports; it is difficult that every export coexists with others. There are exports that have a `require('fs')` _(or other node things)_ and although webpack does tree-shaking,...
Ok this sounds really good 🙏
@wuifdesign I guess that changing this `catch` https://github.com/vinissimus/next-translate/blob/7531ff2c4a53f32a9fb15317e490311c5cf84bf4/src/loadNamespaces.tsx#L51 to line 48 will fix this. Feel free to PR.
@keilind you do not need to have the language within a directory within pages, this is managed by the[ i18n routing of Next.js](https://nextjs.org/docs/advanced-features/i18n-routing). So instead of: ``` pages ├── en...
Probably related with this issue? https://github.com/vinissimus/next-translate/issues/486
A simple workaround would be to load it manually: ```js import i18n from '../i18n' global.i18nConfig = i18n ``` Before solving it, I would like to rethink the way of consuming...
@Marc-Hoch the project is open-source, feel free to implement and do a PR
@piiok `DynamicNamespace` loads the files that you specify... Did you try something like this? ```js import React, { useState } from 'react' import Trans from 'next-translate/Trans' import DynamicNamespaces from 'next-translate/DynamicNamespaces'...
@piiok did you finally solve the problem?