next-i18next: Keep getting: "You have not declared a namespacesRequired array on your page-level component: undefined"

You 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?

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (8 by maintainers)

Most upvoted comments

I solved this issue by providing favicon.ico, which was adding 404 error and causing this warning.

I solved this issue by providing favicon.ico, which was adding 404 error and causing this warning.

@laxplaer Thanks for the fix!

I think by placing a favicon.ico (or resolving any 404) you are only sidestepping the issue; you’re not actually resolving the underlying issue that your error handler is not namespacing like it should. Right?

@isaachinman I have the same warning with next.js@9.5.5. If I create 404.js page and _error.js I see this warning. If I remove 404.js I see a warning from next.js Warning: You have added a custom /_error page without a custom /404 page. This prevents the 404 page from being auto statically optimized. See here for info: https://err.sh/next.js/custom-error-no-custom-404 How to fix it?)