-
Notifications
You must be signed in to change notification settings - Fork 36
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
Adapt scripts to npm package manager #131
Comments
rschnekenbu
added a commit
to rschnekenbu/vscode-builtin-extensions
that referenced
this issue
Oct 9, 2024
Also updates builtin to 1.94.0 fixes eclipse-theia#131 contributed on behalf of STMicroelectronics Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
rschnekenbu
added a commit
to rschnekenbu/vscode-builtin-extensions
that referenced
this issue
Oct 30, 2024
Also updates builtin to 1.94.2 fixes eclipse-theia#131 contributed on behalf of STMicroelectronics Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
rschnekenbu
added a commit
to rschnekenbu/vscode-builtin-extensions
that referenced
this issue
Nov 26, 2024
Also updates builtin to 1.94.2 fixes eclipse-theia#131 contributed on behalf of STMicroelectronics Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
rschnekenbu
added a commit
that referenced
this issue
Nov 26, 2024
Also updates builtin to 1.94.2 fixes #131 contributed on behalf of STMicroelectronics Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VSCode now relies on npm rather than yarn as a package manager (see https://code.visualstudio.com/updates/v1_94#_use-npm-as-default-package-manager).
Builtins build process still relies on vscode using yarn, as for example
vscode-builtin-extensions/package.json
Line 5 in 156de19
The text was updated successfully, but these errors were encountered: