New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.1 requires node >= 16.0 but the documentation still says 12 #181
Labels
question
Question instead of bug/feature-request
Comments
Projects should upgrade to Node 16. This is the version that VS Code runs in its extension host, so being on that version would ensure a consistent environment and avoid surprises. Node 12 is also end of life and no longer receives security updates. |
connor4312
added a commit
that referenced
this issue
Dec 6, 2022
connor4312
added a commit
that referenced
this issue
Dec 6, 2022
Node 14 is still under LTS maintenance, though, and dropping support for it in a patch release wasn't ideal 😕 |
dfreeman
added a commit
to typed-ember/glint
that referenced
this issue
Dec 7, 2022
hmajoros
pushed a commit
to hmajoros/glint
that referenced
this issue
Dec 15, 2022
aeschli
added a commit
to microsoft/vscode-generator-code
that referenced
this issue
Jan 31, 2023
aeschli
added a commit
to microsoft/vscode-generator-code
that referenced
this issue
Jan 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The newly released 2.2.1 version of the
@vscode/test-electron
package requires node >= 16, but the readme still saysNode >= 12.x
.Will this requirement be loosened, or should projects either upgrade to Node 16 or pin vscode/test-electron to 2.2.0?
The text was updated successfully, but these errors were encountered: