-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fix "res.writeHead is not a function" in Express/node middleware #7708
Conversation
🦋 Changeset detectedLatest commit: a8e1272 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Thanks so much for the PR, we really appreciate it! This change looks good but there seems to be a type error. Once that's fixed, this should be good to go! |
i forgot to build before submit, i will fix it |
My idea is that I need to infer the type of parameters received by the handler in createExports in runtime🤔 |
That seems to be overcomplicating things? Couldn't the handler accept any number of arguments ( |
Like |
Yeah that's the idea |
I committed it with this idea |
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.
Thanks for making that change, this looks great!
Changes
Fix #7590
add "error" argument to nodeMiddleware handler function
Testing
#7590 works correctly
Docs
bug fix