CodeSampleX

Recordsnpm@prisma/fetch-engine6.19.0

Change the conditions
Fixed
OSubuntu glibc Package version6.19.0
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@prisma/fetch-engine @6.19.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

6.19.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster
Library Version Health Measured there Projects
@prisma/debug 6.19.0 PASS All observations passed contract passed 4 project-days
@prisma/engines-version 6.19.0-26.2ba551f319ab1df4bc874a89965d8b3641056773 PASS All observations passed contract passed 4 project-days
@prisma/get-platform 6.19.0 PASS All observations passed 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.