-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Dynamic routing (directory param) doesn't work on the custom server #8092
Comments
Without a full reproduction provided there's nothing we can do to help debug your setup. |
@Timer I just created a simple example demonstrating the issue I just added a new page with dynamic routing and if you run app, navigate in browser directly to http://localhost:3000/post/5 your url will be transformed into: http://localhost:3000/post/[id]?id=%5Bid%5D So issue is pretty stable and easy to reproduce All changes I've made are here: adascal/next-i18next@a6866a2 I used existing example from Maybe @isaachinman can look as well |
I've made a fix here: i18next/next-i18next#422 Hope to be merged soon |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Bug report
Describe the bug
I have the following
pages
structure:This should work according to the blog article:
The router seems to redirect correctly on the client side, however I get the following url for the server-side:
I have a custom express server setup (to enable next-i18next):
I also added a route handler just in case. The route is being caught by the handler but the outcome is same.
To Reproduce
I use the combination of the following examples:
plus TypeScript
Expected behavior
I expect the dynamic routing works properly.
Screenshots
(none)
System information
Additional context
(none)
The text was updated successfully, but these errors were encountered: