Keep getting: "You have not declared a namespacesRequired array on your page-level component: undefined"
See original GitHub issueYou have not declared a namespacesRequired array on your page-level component: undefined. This will cause all namespaces to be sent down to the client, possibly negatively impacting the performance of your app. For more info, see: https://github.com/isaachinman/next-i18next#4-declaring-namespace-dependencies
I keep getting the following error but I feel like I have namespacesRequired
on all my page level components.
Can someone help figure out where this is actually talking about so I can get to the bottom of it?
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (8 by maintainers)
Top Results From Across the Web
"You have not declared a namespacesRequired array on your ...
You have not declared a namespacesRequired array on your page-level component: undefined. This will cause all namespaces to be sent down to the...
Read more >i18next - How to avoid the “You have not declared a ...
You have not declared a namespacesRequired array on your page-level component: Home. This will cause all namespaces to be sent down to the...
Read more >next-i18next - npm
Passing in an empty array of required namespaces will send no namespaces. Note: useTranslation provides namespaces to the component that you use ...
Read more >Analyst Custom Searches - Internal Server Error - Forums - IBM ...
You have not declared a namespacesRequired array on your page-level component: Index. This will cause all namespaces to be sent down to the...
Read more >next-i18next setup in next.js for multi-languages implementation
Must create namespacesRequired (Array) in each Component. pages/index.js. this.props.t("description") to get the locale content. i18n.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I solved this issue by providing
favicon.ico
, which was adding 404 error and causing this warning.@laxplaer Thanks for the fix!