chore: switch yarn to npm #2131
Merged
Conversation
This file contains 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
|
|
|
But another thing to install besides node. I'll move to npm for now and maybe at some point we can consider pnpm for all of the Vega projects. I want to be consistent, though. |
|
Moving ahead since npm install is 20s which is way faster than the 6m for tests. moving away from yarn is important since many people get confused that they need to install an old version (v1) of yarn.
|
|
makes sense! good decision :) |
|
🚀 PR was released in |
This was referenced Jan 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📦 Published PR as canary version:
2.3.1--canary.2131.2f5e0d3.0✨ Test out this PR locally via: