Polyfill headers in connect-node #462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mostly yeah. I can merge in the versions you're using in 459 though if you'd like (including the use of a MIN_VERSION) |
timostamm
approved these changes
Feb 15, 2023
There was a problem hiding this comment.
Nice! Does this replace #459 ?
Mostly yeah. I can merge in the versions you're using in 459 though if you'd like (including the use of a MIN_VERSION)
Don't have a strong opinion on the exact versions, as long as we test the lowest one we have in the engines field.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This a few things regarding connect-node and the versions supported by the framework:
connect-nodeinstead of the test package. This will automatically polyfill connect-node for users on versions less than 18.enginedefinition to our package.json for Node versions.