Upgrade to Yarn 4#3975
Conversation
🦋 Changeset detectedLatest commit: 5332c31 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
d28fc30 to
f45aede
Compare
|
@benjie the LSP integration test suite is failing because it appears that the fetch mocking is failing, and the monaco build test is something you can ask @dimaMachina about, but it looks like it's now asserting the wrong line after a vite upgrade I think? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3975 +/- ##
==========================================
+ Coverage 63.94% 63.97% +0.03%
==========================================
Files 35 35
Lines 3087 3087
Branches 950 948 -2
==========================================
+ Hits 1974 1975 +1
+ Misses 1108 1107 -1
Partials 5 5
🚀 New features to boost your workflow:
|
…usted maintainers should update it)
|
The latest changes of this PR are available as canary in npm (based on the declared |
| // `--no-colors` flag | ||
| const lines = stdout.replaceAll(ANSI_COLOR_REGEX, '').split('\n'); | ||
| // expect(lines[0]).toBe('$ vite build'); | ||
| // expect(lines[1]).toMatch(' building for production...'); |
There was a problem hiding this comment.
This line is no longer output.
Yarn 1.x entered maintenance mode in January 2020; time to upgrade.
This PR does minimal changes, it's based on the setup I use in the Graphile Crystal monorepo which I've been running without issues for years.
Depends on:
closes #2185 #3306 #3303