Usable catch all route

[pbortnick]

Any suggestions on what to do if you actually want a working [locale]/[...rest]/page.tsx? I need a catch all route that actually displays content and doesn't just act as a safety net for notFound() 404s.

Pages that exist are working fine but when I hit an unexpected page or one that ends in .txt for example, I'm getting all kinds of errors.

Note: this route is inside of a route group which seems to be causing all sorts of issues (#800).

[amannn]

Do you think you could show an example based on next-intl-bug-repro-app-router to illustrate this?

Generally, such a [...rest] page should work. Depending on your setup, one potential cause of an issue could be if your middleware matcher doesn't match .txt. See pathnames without a locale prefix in the docs.

As a side note, the Next.js team is working on rootParams, an API that next-intl will benefit of greatly. It's also expected to work with route groups.

[pbortnick]

rootParams will be great! I appreciate your responsiveness @amannn and I look forward to following along as next-intl keeps growing

[pbortnick]

I actually did get it to work. There was a bug because my code was trying to fetch using locale as a variable before hitting the 404. Difficult to explain but I will get a minimal repro up as soon as I have a chance to help fellow next-intl users if anyone else runs into something similar! 😃