Is static error pages with locale support not supported for pages router? #2061
cupofjoakim
started this conversation in
General
Replies: 1 comment
-
|
I've just added a 404 page to the Pages Router example in #2062 and didn't really encounter any issues. Can you elaborate on what exactly the issue is that you're seeing? A minimal reproduction might help. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
We're trying to migrate our app using pages router to next-intl before we start moving over to the app router. We have up until this point relied on nextjs's own i18n config.
One feature that we're struggling to figure out is static page generation on 404's and 500's with locale support. The documentation is very app-router centric, and the examples don't really cover i18n in error pages.
As a base question: Can we somehow statically generate error pages with locales in the pages router using next-intl?
If not, can we do it in the app router while still triggering them from the pages router? i.e. a 500 is thrown from a pages route, resulting in the app router error page to show?
Beta Was this translation helpful? Give feedback.
All reactions