Ensure custom routes handling with i18n (#18427)
This makes sure custom-routes function properly with i18n support. Since the `locale` is stripped from the `pathname` this re-adds when checking custom-routes to allow the locale to be matched against Closes: https://github.com/vercel/next.js/issues/18349
Showing
Please
register
or
sign in
to comment