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.

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

Move vscode builtin production from yarn to npm #132

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rschnekenbu
Copy link

@rschnekenbu rschnekenbu commented Oct 9, 2024

Migrate the package manager of VS Code from yarn to npm
Also updates to vscode subrepo to 1.94.2, as this is the first version to rely on npm.

fixes #131

contributed on behalf of STMicroelectronics

@tsmaeder
Copy link
Contributor

@rschnekenbu is there documentation that needs to be updated with this change?

@rschnekenbu
Copy link
Author

@tsmaeder, probably some README or how-to-build documentation to update, indeed. I will update this PR

Also updates builtin to 1.94.2

fixes eclipse-theia#131

contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <[email protected]>
@rschnekenbu
Copy link
Author

rschnekenbu commented Oct 30, 2024

@tsmaeder, I updated the documentation, some commands now relying on npm rather than yarn on vscode repo.
This vscode-builtin-extensions repository still uses yarn v1 of course, so many of the building commands and all publishing ones are still yarn based.

I took also the opportunity to update the vscode commit ref to tag 1.94.2 (current latest release on 1.94 stream). I also updated some part of the documentation that had some markdown formatting issues or warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adapt scripts to npm package manager
2 participants