Recordsnpmexpress
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| 5.2.1 | 5.1.0 | 4.22.2 | 4.21.2 | 4.21.0 | 4.19.1 | |
|---|---|---|---|---|---|---|
| express | 100%8 | 100%8 | 100%4 | 100%4 | 100%4 | 100%4 |
| Router shared ×2 | — | — | ||||
| app.router | — | |||||
| app.use | — | — | ||||
| express | — | — | — | — | — | |
| res.format | — | — |
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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 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 | 5.2.1 | 5.1.0 |
|---|---|---|
| accepts | 2.0.0 | 2.0.0 |
| body-parser | 2.3.0 | 2.3.0 |
| content-disposition | 1.1.0 | 1.1.0 |
| content-type | 1.0.5 | 1.0.5 |
| cookie | 0.7.2 | 0.7.2 |
| cookie-signature | 1.2.2 | 1.2.2 |
| debug | 4.4.3 | 4.4.3 |
| depd | 2.0.0 | — |
| encodeurl | 2.0.0 | 2.0.0 |
| escape-html | 1.0.3 | 1.0.3 |
| etag | 1.8.1 | 1.8.1 |
| finalhandler | 2.1.1 | 2.1.1 |
| fresh | 2.0.0 | — |
| http-errors | 2.0.1 | — |
| merge-descriptors | 2.0.0 | — |
| mime-types | 3.0.2 | — |
| on-finished | 2.4.1 | — |
| once | 1.4.0 | — |
| parseurl | 1.3.3 | — |
| proxy-addr | 2.0.7 | — |
| qs | 6.15.3 | — |
| range-parser | 1.3.0 | — |
| router | 2.2.0 | — |
| send | 1.2.1 | — |
| serve-static | 2.2.1 | — |
| statuses | 2.0.2 | — |
| type-is | 2.1.0 | — |
| vary | 1.1.2 | — |
Moved: 0 · unchanged at every release: 28
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.