CodeSampleX

Recordsnpm@tailwindcss/node4.3.3

Change the conditions
Fixed
OSdebian glibc Symbolwhole package
Filter Runtimenode 22 Package version4.3.3 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@tailwindcss/node @4.3.3debian glibc · x64 · node 22 · npm · 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.

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

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

4.3.3

linux · node@22.23 · executionContext=node · moduleSystem=cjs

1 FAIL · stage: UNKNOWN · fingerprint: sha256:63456a9a1a17407c9902ebcc47325a21e7f345ec8d2ad299da2b4fd68b1dd29b

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jridgewell/remapping 2.3.5 PASS All observations passed contract passed 6 project-days
enhanced-resolve 5.24.5 PASS All observations passed contract passed 4 project-days
enhanced-resolve 5.25.1 PASS All observations passed contract passed 2 project-days
jiti 2.7.0 PASS All observations passed contract passed 6 project-days
lightningcss 1.32.0 PASS All observations passed contract passed 6 project-days
magic-string 0.30.21 PASS All observations passed contract passed 6 project-days
source-map-js 1.2.1 PASS All observations passed contract passed 6 project-days
tailwindcss 4.3.3 PASS All observations passed contract passed 6 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.

Recent failure clusters