-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
docs: add v5 migration note for app.listen #1705
base: gh-pages
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for expressjscom-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great
ae63d87
to
40e9db5
Compare
Adds a note to the `migrating-5` guide alerting users that error events received by a server will now cause the callback argument in `app.listen` to be invoked. In Express 4, this was not the case and errors would be thrown. Resolves expressjs/express#6191 Signed-off-by: Dustin Popp <[email protected]> Co-authored-by: M. Heide <[email protected]>
40e9db5
to
a042fc7
Compare
@bjohansebas @carlosstenzel thanks for reviewing! I cleaned up the linter errors. Is there anything I can do to fix the "Check Translation" build step failure? |
Hi @dpopp07, don't worry about the Check Translation workflow, it will always fail for PRs coming from a fork. I think this workflow should be removed |
@bjohansebas Great - I thought that might be the case but wanted to confirm you didn't need anything else from me. Thanks! |
Adds a note to the
migrating-5
guide alerting users that error events received by a server will now cause the callback argument inapp.listen
to be invoked. In Express 4, this was not the case and errors would be thrown.Resolves expressjs/express#6191
Any feedback, rewording, etc. is welcome!