NodeJSManager wrongly claims Node 16 is not supported #837
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
And we shipt Node.js 16.x as our bundled. The idea of static list of supported versions is plain wrong as we have no idea which editor which version of Node.js supports it's best to remove the static list and just say "recent" version is required when using the "system" Node.
|
Uncovered by Linux Tools build stuck at the Message dialog claiming Node.js 16 is not supported version. https://ci.eclipse.org/linuxtools/job/linuxtools/job/master/65/console |
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.
And we shipt Node.js 16.x as our bundled.
The idea of static list of supported versions is plain wrong as we have
no idea which editor which version of Node.js supports it's best to
remove the static list and just say "recent" version is required when
using the "system" Node.