Recordsnpmtailwindcss
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| 3.4.17 | |
|---|---|
| tailwindcss shared ×2 | 100%6 |
| tailwindcss/plugin shared ×2 | — |
| tailwindcss/resolveConfig shared ×2 | — |
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| postcss | 8.4.49 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| postcss-load-config | 4.0.2 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| postcss-selector-parser | 6.1.4 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| resolve | 1.22.12 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| sucrase | 3.35.1 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| @alloc/quick-lru | 5.2.0 | PASS All observations passed | contract passed | 1 project-day |
| arg | 5.0.2 | PASS All observations passed | contract passed | 1 project-day |
| chokidar | 3.6.0 | PASS All observations passed | contract passed | 1 project-day |
| didyoumean | 1.2.2 | PASS All observations passed | contract passed | 1 project-day |
| dlv | 1.1.3 | PASS All observations passed | contract passed | 1 project-day |
| fast-glob | 3.3.3 | PASS All observations passed | contract passed | 1 project-day |
| glob-parent | 6.0.2 | PASS All observations passed | contract passed | 1 project-day |
| is-glob | 4.0.3 | PASS All observations passed | contract passed | 1 project-day |
| lilconfig | 3.1.3 | PASS All observations passed | contract passed | 1 project-day |
| micromatch | 4.0.8 | PASS All observations passed | contract passed | 1 project-day |
| normalize-path | 3.0.0 | PASS All observations passed | contract passed | 1 project-day |
| picocolors | 1.1.1 | PASS All observations passed | contract passed | 1 project-day |
| postcss-import | 15.1.0 | PASS All observations passed | contract passed | 1 project-day |
| postcss-js | 4.1.0 | PASS All observations passed | contract passed | 1 project-day |
| postcss-nested | 6.2.0 | PASS All observations passed | contract passed | 1 project-day |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.
Moved: 5 · unchanged at every release: 17
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.