Aral Roca Gomez
Aral Roca Gomez
@devaquila Ok, I reopen. Does it happen only with custom server? Tomorrow I'll try the example, I'm not at my computer right now.
@dcodus thanks for that suggestion. I noted to 1.1
You can use the [getT](https://github.com/vinissimus/next-translate#gett) on Node.js: ```js import getT from 'next-translate/getT' // ... export async function getStaticProps({ locale }) { const t = await getT(locale, 'common') const title =...
`locale` is provided inside `getStaticProps` arguments by Next.js
Not for now. What advantages does it have over interpolation? The same can be done with: Text: ``` { "my-name": My name is {{username}} } ``` Code: ```js const {...
@BjoernRave in the latest version 0.20.2 you can do this: ```js const { t } = useTranslation('common') // Default namespace const text = t('hello') // No need to use common:...
Do you mean as a fallback if the namespace doesn't match? ```js const { t } = useTranslation('some-namespace') const text = t('hello') // "some-namespace:hello", if doesn't exist then return "common:hello"...
Ok @BjoernRave, I marked as a future feature, surely for the 1.1, since we are closing the 1.0! Thank you for the proposal
I think (not sure) that right now it could be configured like this. ```js { // ...rest of config "loadLocaleFrom": async (lang, ns) => { const ns = await import(`./locales/${lang}/${ns}.json`).then((m)...
E-commerce has to go fast, Adyen slows us down, it is currently the largest piece of JavaScript in our project, would it be possible to dedicate to reduce this size?...