test(snapshots): isolate npm network cases - #2604
Merged
Merged
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
cpojer
approved these changes
Sep 4, 2026
fengmk2
force-pushed
the
fix/npm10-migration-peer-resolver
branch
from
September 4, 2026 02:13
e46024e to
9fb24ab
Compare
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
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.
The snapshot runner starts network-dependent npm cases in parallel. This load can open 64 HTTPS connections. A command can then time out without output.
Run npm 10 cases alone. Make
serial = truework acrosscargo testthreads and Windows nextest processes.Keep the npm 10 coverage. Upgrade only
migration_standalone_npmtonpm@11.13.0, because npm 10 fails withedgesOutin this fixture.