-
-
Notifications
You must be signed in to change notification settings - Fork 17.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
The max sync stack
is breaking routing
#4899
Comments
Hi @minghaopu63 the limit is not a max number of routes or anything. You can still have an infinite about. Can you provide a reproduction case the demonstrates what broke? The change should be transparent, so the fix would make it work the same as before. |
max sync stack
limitation should be configurablemax sync stack
limitation should be configurable
max sync stack
limitation should be configurablemax sync stack
breaking routing
max sync stack
breaking routingmax sync stack
is breaking routing
Hi @dougwilson, here is a repo i just set up to reproduce the issue. https://github.com/minghaopu63/express-test. After clone, you can run the following steps to reproduce this.
|
Thank you, this was very helpful! I see what the issue is. I will have a 4.18.1 out ASAP with the fix. You are awesome!!! |
Ok, fix published as version 4.18.1 🎉 |
Thanks! |
We recently updated to v4.18.0 and find some routes are not working anymore due to 708ac4c.
100
limitation is not in the change log http://expressjs.com/en/changelog/4x.html#4.18.0. Can you help update it?Thanks
The text was updated successfully, but these errors were encountered: