CodeSampleX

Recordsnpmreact-i18next15.7.4react-i18next.I18nextProvider

Change the conditions
Fixed
Runtimenode 22 Symbolreact-i18next.I18nextProvider
Filter OSubuntu glibc Package version15.7.4 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

react-i18next.I18nextProvider @15.7.4ubuntu glibc · x64 · node 22 · npm 10 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

15.7.4

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

3 FAIL · stage: UNKNOWN · fingerprint: sha256:c113861ea6575a55f8e3a44f91634852da7cbcd3825a7f52264c417b812b7599

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/runtime 7.29.7 PASS All observations passed contract passed 4 project-days
html-parse-stringify 3.1.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.