-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Migrate to Node 18 #6230
Comments
We can do this once VS Code updates to Node 18. |
microsoft/vscode#180466 |
do you have any information on when it would be available ? september is near. |
We are waiting on vscode to migrate first |
Yes, but looks like it will not be available for several month. Internally they are afraid of moving to electron 25.... meanwhile, node 16 and openssl1.1.1 is ending in september >< Thank you, I'm crossing my finger. For information, i'm bumping all my jupyterlab stack to 4.0 and node 18 is asked (but looks like not mandatory) anyway, I have the same issue with openssl 1.1.1 VS 3 >< |
@skapin I stay with v3.6.x for my JupyterLab docker stacks because of jupyterlab/jupyterlab#14590. |
@benz0li yeah, but my release plan is for sept/october, and I want to do it early, at least maximize compatibility. It's out for several months now. I will clean old extension and co. Cleaning time :p |
ℹ️ Update to Electron 25 (Issue: microsoft/vscode#184021; Pull Request: microsoft/vscode#188268) is part of the Iteration Plan for August 2023 [DRAFT]. |
One particularly important reason for pressing Microsoft's VSCode team on this is this specific change is required to eliminate a number of Critical and High scoring CVE's, and there is a risk in many high compliance environments that these codebases could be delisted from authorized lists if this doesn't happen quickly. We are seeing this happen in real time with a certain Australian company who make Agile process management software. Missions in the federal government are being told to immediately isolate and cut off all access to these systems. This is a pretty dark stain on any closed source or OSS solution. |
What is your suggestion?
Migrate code-server to use nodejs 18 instead of 16
Why do you want this feature?
nodejs 16 reaches EOL on september 2023 https://nodejs.org/en/blog/announcements/nodejs16-eol
Are there any workarounds to get this functionality today?
Are you interested in submitting a PR for this?
I might look into making this work in a few months from now
The text was updated successfully, but these errors were encountered: