Skip to content
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

Closed
minghaopu63 opened this issue Apr 27, 2022 · 5 comments
Closed

The max sync stack is breaking routing #4899

minghaopu63 opened this issue Apr 27, 2022 · 5 comments

Comments

@minghaopu63
Copy link

We recently updated to v4.18.0 and find some routes are not working anymore due to 708ac4c.

  1. This 100 limitation is not in the change log http://expressjs.com/en/changelog/4x.html#4.18.0. Can you help update it?
  2. Can this value be configurable?

Thanks

@dougwilson
Copy link
Contributor

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.

@dougwilson dougwilson changed the title [Feature Request] The max sync stack limitation should be configurable The max sync stack limitation should be configurable Apr 27, 2022
@dougwilson dougwilson changed the title The max sync stack limitation should be configurable The max sync stack breaking routing Apr 27, 2022
@dougwilson dougwilson changed the title The max sync stack breaking routing The max sync stack is breaking routing Apr 27, 2022
@minghaopu63
Copy link
Author

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.

  1. npm i
  2. npm run build
  3. npm start
  4. visit http://localhost:3000/abcd

@dougwilson
Copy link
Contributor

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!!!

@dougwilson
Copy link
Contributor

Ok, fix published as version 4.18.1 🎉

@minghaopu63
Copy link
Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants