CodeSampleX

Recordsnpm@tailwindcss/node

Change the conditions
Fixed
Package version4.3.3 Symbolcompile
Filter Runtimenode 22 Architecturex64 Execution contextnode Clear filters

Current conditions

compile @4.3.3x64 · node 22 · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-08-20

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

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 · moduleSystem=cjs · executionContext=node

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

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.