feat: drop node v10 support #163
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
fastify-reply-from v6 is dropping support of node v10 ref: fastify/fastify-reply-from#179
|
Could you also bump fastify-http-proxy |
|
@mcollina Thanks for a quick response! 😄 just bumped the version on package.json to |
|
I'm sorry I should not have asked for that.. I meant bumping fastify-reply-from. no big deal anyway. |
mcollina
reviewed
Jun 27, 2021
|
np. I'll wait for the next release 👀 |
3 tasks
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.
undiciv4 dropping support of node v10, andfastify-reply-fromv6 relies on that.fastify-http-proxyalso affected by this after #162.I am experiencing something similar to #136 currently, so I hope to use
undiciv4'sstrictContentLengthoption in the next major release 😄ref:
Checklist
and the Code of conduct