-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
feat: migrate to node 16.14.0 (lts) #219
Conversation
kettanaito
commented
Mar 1, 2022
•
edited
Loading
edited
- Closes What versions of node do we want to support? #217
- Updates to Node.js 16.14.0 as the officially supported version.
- Updates any related dependencies.
c4c33e6
to
bf0ade6
Compare
this.observer.emit('response', isomorphicRequest, isomorphicResponse) | ||
// Execute the resolver Promise like a side-effect. | ||
// Node.js 16 forces "ClientRequest.end" to be synchronous and return "this". | ||
until(async () => this.resolver(isomorphicRequest, this.response)).then( |
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.
Resolver execution is a side-effect right now. This needs to be tested.
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.
Automated tests report no issues. Response handling logic is asynchronous by design. I think when Node 16 forced end
to return this
they accounted for it. As in: return the next (potentially unresolved) state of ClientRequest
.
The |
b55e201
to
0de3e6d
Compare
Need to publish 7d8f6bd first. |
0de3e6d
to
cf678f5
Compare
cf678f5
to
8074fcb
Compare
🎉 This PR is included in version 0.14.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |