404 route not found on "as-needed" strategy #1210
mehrdad-shokri
started this conversation in
General
Replies: 1 comment
-
|
My first guess would be that this troubleshooting section could help you: Unable to find next-intl locale because the middleware didn't run on this request. |
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
-
I'm switching from the default routing strategy to "as-needed" strategy. I have a
[locale]directory in the root that catches the route segment. after switching to "as-needed" I get 404 when trying to visit/dashboard/chatsI guess that is expected because Next.js can't find that route (it should start with a route segment) I searched though documentation and it's not mentioned how to solve this issue. Can someone elaborate on this? Thank youBeta Was this translation helpful? Give feedback.
All reactions