VS Code main has moved back to npm, we could catch it#148
Merged
aeschli merged 1 commit intomicrosoft:mainfrom Nov 18, 2024
Merged
VS Code main has moved back to npm, we could catch it#148aeschli merged 1 commit intomicrosoft:mainfrom
aeschli merged 1 commit intomicrosoft:mainfrom
Conversation
Cecil0o0
changed the title
aeschli
approved these changes
Nov 18, 2024
Collaborator
|
Thanks @Cecil0o0 ! |
bpasero
approved these changes
Nov 18, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our main repository of VS Code has moving back to npm, about this issue
I found that
yarn compilecould work if you have already installedyarnglobally on your local machine, so even if somebody follows thisREADME.mddocumentation, he/she still could get compiled for VS Code, however else could not instead.