Drop support for node v12 #299
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
|
@lo1tuma should this be related to #298 (comment)? If Node 12 support is dropped, maybe we should release new major version? |
|
@lo1tuma can I ask why Node 12 completely was dropped? It's still in maintenance LTS until 2022-04-30 and eslint 8 supports |
|
@WikiRik usually I consider to drop support for older node versions every time I’m planning to make a new major-version release. The EoL for node 12 is in only 4 months, so I think it is reasonable for people who still want to use node 12 until then to also use an older version of |
|
@lo1tuma I can see that. Thanks for the quick response! |
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.
No description provided.