New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using middleware with base path #38528
Comments
I think this might be what I'm seeing! I walked through the code and found that 12.1.7 introduced some logic that removed the query params, and downgrading to 12.1.6 fixed it for me: d959d28#r83332647 |
just checked: this error still occurs in 12.3.0 (which makes sense, since it was still present in canary), but i was hoping because router changes were in the release log |
* Ensure client cache keys match between prefetch and transition * handle some middleware cases * lint-fix * fix lint rename
…sePath option is truthy (#40566) ## Bug - [x] Related issues linked using `fixes #number` - fixes - #38528 - #40432 - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Hi, it is my first pull request in this project. So... if you need anything more tasks, please tell me. Co-authored-by: JJ Kasper <22380829+ijjk@users.noreply.github.com>
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
What browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
Describe the Bug
I added in my next config a basePath. I use the middleware example here https://nextjs.org/docs/advanced-features/i18n-routing for adding the default locale. by doing this all pages with a query are empty. If I remove the middleware everything works.
Expected Behavior
Link to reproduction
https://github.com/magsout/repro-middleware-nextjs
To Reproduce
if you comment the middleware, no issue at all.
The text was updated successfully, but these errors were encountered: