-
Notifications
You must be signed in to change notification settings - Fork 27.4k
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 behaves differently in Dev vs Prod #7880
Comments
@brunolemos your page is likely being statically optimized, meaning it was prerendered without any query parameters -- in production, this means your page isn't being rendered on-request (SSR). The page will hydrate on the client and trigger the router update, at which point you can handle the autostart feature. |
Got it! My bad, I was using |
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. |
In dev, prerendered pages have their queries empty. In prod, the queries are the placeholders
[param]
.The desired behavior is for both of these to be empty. Not sure if we should use
undefined
,null
, or''
.I'm leaning towards
null
or empty string.This must have a failing test added in a PR before it can be fixed.
The text was updated successfully, but these errors were encountered: