Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Node 20 Support #1580

Closed
pastuxso opened this issue Aug 21, 2024 · 1 comment · Fixed by #1696
Closed

Node 20 Support #1580

pastuxso opened this issue Aug 21, 2024 · 1 comment · Fixed by #1696
Assignees

Comments

@pastuxso
Copy link
Contributor

pastuxso commented Aug 21, 2024

Recently, I noticed how our dependency modules are moving to Node 20. For example: microsoft/vscode-vsce#1035 #1567

Right now, the unique blocker is the usage of the --experimental-specifier-resolution=node, which starting from Node v19 has been deprecated. To replace it requires the usage of loaders like https://github.com/barhun/extensionless, which enables support to import modules without the file extension. In our case, modules from Buf are using relative imports without file extensions.

@sourishkrout
Copy link
Member

More importantly we should probably track with VS Code's Electron/Node version:

Version: 1.92.2 (Universal)
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0

@pastuxso pastuxso changed the title [Draft] Node 20 Support Node 20 Support Oct 1, 2024
@pastuxso pastuxso self-assigned this Oct 1, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants