CodeSampleX

Recordsnpmbabel-preset-current-node-syntax

there is a sample for this release and API (1)

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version1.2.0 Symbolwhole package
Filter Architecturex64 Execution contextnode Clear filters
OS × Runtime
1 1 12026-08-31
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.

Dependencies

LibraryVersionMeasured thereProjects
@babel/plugin-syntax-async-generators 7.8.4 contract passed 7 project-days
@babel/plugin-syntax-bigint 7.8.3 contract passed 7 project-days
@babel/plugin-syntax-class-properties 7.12.13 contract passed 7 project-days
@babel/plugin-syntax-class-static-block 7.14.5 contract passed 6 project-days
@babel/plugin-syntax-import-attributes 7.29.7 contract passed 5 project-days
@babel/plugin-syntax-import-meta 7.10.4 contract passed 5 project-days
@babel/plugin-syntax-json-strings 7.8.3 contract passed 5 project-days
@babel/plugin-syntax-logical-assignment-operators 7.10.4 contract passed 5 project-days
@babel/plugin-syntax-nullish-coalescing-operator 7.8.3 contract passed 5 project-days
@babel/plugin-syntax-numeric-separator 7.10.4 contract passed 5 project-days
@babel/plugin-syntax-object-rest-spread 7.8.3 contract passed 4 project-days
@babel/plugin-syntax-optional-catch-binding 7.8.3 contract passed 4 project-days
@babel/plugin-syntax-optional-chaining 7.8.3 contract passed 4 project-days
@babel/plugin-syntax-private-property-in-object 7.14.5 contract passed 4 project-days
@babel/plugin-syntax-top-level-await 7.14.5 contract passed 4 project-days

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.