Compatibilitynpmvite8.2.1vi.advanceTimersByTimeAsync
Change the conditions
Current conditions
vi.advanceTimersByTimeAsync @8.2.1alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-18
Dependencies
Nothing has resolved this release yet, so its dependencies are unread rather than empty. See where it is counted
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 8.2.2 | 7.3.6 | 6.4.3 | 5.4.21 |
|---|---|---|---|---|
| esbuild | — | 0.28.2 | 0.25.12 | 0.21.5 |
| picomatch | 4.0.7 | 4.0.5 | 4.0.7 | — |
| rollup | — | 4.63.1 | 4.63.0 | 4.63.1 |
| fdir | — | 6.5.0 | 6.5.0 | — |
| lightningcss | 1.33.0 | — | — | — |
| postcss | 8.5.26 | 8.5.26 | 8.5.26 | 8.5.26 |
| rolldown | 1.2.6 | — | — | — |
| tinyglobby | 0.2.17 | 0.2.17 | 0.2.17 | — |
Moved: 3 · unchanged at every release: 5
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×5 7.3.6 → 8.2.1 executionContext=node · moduleSystem=esmEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-30Diagnostic re-verification candidate