Aral Roca Gomez

I'm not sure how fast-refresh works, I'll have to investigate. But the truth is that it would be good if the change was automatic reflected without having to refresh. Thanks...

I guess is related to https://github.com/vercel/next.js/discussions/15521 fast refresh doesn't work on getStaticProps (where the translations are loaded). Let's see if we can find a solution.

@vahidtakro Please would you give more details of the error or an example reproducing it? Thanks

@jahirfiquitiva You can configure it by doing the following: ```js { // ...rest of config "loadLocaleFrom": async (lang, ns) => { const locales = await import(`./locales/${lang}/${ns}.json`).then((m) => m.default) const defaultLocales...

As an idea, maybe it would work using the `dynamic` prop that you added with `() => Promise.resolve({ namespace: { text: 'Test'}})`. It's not necessary to test the `loadLocaleFrom`. I...

This is the default logger, It's possible to fix (as a workaround) providing a custom [`logger`](https://github.com/vinissimus/next-translate/tree/1.2.0#3-configuration). However, it will be good to resolve it. Feel free to PR: https://github.com/vinissimus/next-translate/blame/cb783038fc1674efe7c6fe69b9daaf1e75f2f929/src/transCore.tsx#L220

Yes, you can use the `defaultTrans` prop https://github.com/vinissimus/next-translate#trans-component

> and if I use the defaultTrans the warning disappear? The correct answer would be yes. If it does not, it would have to be fixed in a PR, and...

It should work yes

I guess that If they are in Portuguese it's because the key does not exist in the namespace and so it shows the value of the default key (which is...