Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Adapt scripts to npm package manager #131

Open
rschnekenbu opened this issue Oct 9, 2024 · 0 comments · May be fixed by #132
Open

Adapt scripts to npm package manager #131

rschnekenbu opened this issue Oct 9, 2024 · 0 comments · May be fixed by #132

Comments

@rschnekenbu
Copy link

rschnekenbu commented Oct 9, 2024 •
edited
Loading

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

"build:extensions": "yarn --cwd vscode && yarn compile:extensions && yarn bundle:extensions",

@rschnekenbu rschnekenbu changed the title * Adapt scripts to npm package manager Oct 9, 2024
rschnekenbu added a commit to rschnekenbu/vscode-builtin-extensions that referenced this issue Oct 9, 2024
@rschnekenbu
Move vscode builtin production from yarn to npm
ec31c74 
Also updates builtin to 1.94.0

fixes eclipse-theia#131

contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <[email protected]>
@rschnekenbu rschnekenbu linked a pull request Oct 9, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move vscode builtin production from yarn to npm rschnekenbu/vscode-builtin-extensions
1 participant
@rschnekenbu