Discontinue support for nodejs 0.x #213
Open
Conversation
This file contains hidden or 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
paladox
changed the title
|
cc @DABH |
paladox
changed the title
|
@Marak at what point (if ever) would you be willing to discontinue support for Node 0.x? Related: https://nodesource.com/node-by-numbers . I believe some of those ancient Node versions might have security issues too. I don't have a strong preference to drop support, but it would provide some benefits (e.g. some dev tools e.g. eslint don't play well with old Node, we can't use ES2015 syntax like |
|
I'm okay with dropping support for I guess we can force new node versions for next major release of colors. Older nodes can always use the previous version if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
See #212