Recordsnpmtailwindcssfailure issue
Failure signature
UNKNOWN exit 1 ENOENT Evidence gap ×1
node:fs:<n> · return binding.writeFileUtf8( · ^ · Error: ENOENT: no such file or directory, open <str>
Evidence quality: complete · node · unclassified-diagnostic · outer node · gap stage-unknown · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:63456a9a1a17…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-14 → 2026-09-14
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 4.3.3 | 3.4.18 | 3.4.17 |
|---|---|---|---|
| postcss | — | 8.5.6 | 8.4.49 |
| postcss-load-config | — | 6.0.1 | 4.0.2 |
| postcss-selector-parser | — | 6.1.2 | 6.1.4 |
| resolve | — | 1.22.11 | 1.22.12 |
| sucrase | — | 3.35.0 | 3.35.1 |
| @alloc/quick-lru | — | 5.2.0 | 5.2.0 |
| arg | — | 5.0.2 | 5.0.2 |
| chokidar | — | 3.6.0 | 3.6.0 |
| didyoumean | — | 1.2.2 | 1.2.2 |
| dlv | — | 1.1.3 | 1.1.3 |
| fast-glob | — | 3.3.3 | 3.3.3 |
| glob-parent | — | 6.0.2 | 6.0.2 |
| is-glob | — | 4.0.3 | 4.0.3 |
| jiti | — | 1.21.7 | — |
| lilconfig | — | 3.1.3 | 3.1.3 |
| micromatch | — | 4.0.8 | 4.0.8 |
| normalize-path | — | 3.0.0 | 3.0.0 |
| object-hash | — | 3.0.0 | — |
| picocolors | — | 1.1.1 | 1.1.1 |
| postcss-import | — | 15.1.0 | 15.1.0 |
| postcss-js | — | 4.1.0 | 4.1.0 |
| postcss-nested | — | 6.2.0 | 6.2.0 |
Moved: 5 · unchanged at every release: 17
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tailwindcss 4.3.3: Ensure --spacing(0) optimizes to 0px in calc expressions and text-[--spacing(...)] infers font-size rather than color This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW--spacing@import tailwindcssnode MIT-0 · 2026-08-16
- tailwindcss 4.3.3: Configure @tailwindcss/postcss with options and prove legacy config requires CSS @config instead of JS options This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW@tailwindcss/postcss@confignode MIT-0 · 2026-08-16
- tailwindcss 4.3.3: Compile Tailwind CSS v4 utilities where numeric spacing scales compile to dynamic calc(var(--spacing) * N) expressions, opacity-50 emits percentage 50%, color opacity uses color-mix() without --tw-bg-opacity, and space-x uses :where() with logical margin-inline properties. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcompilenode MIT-0 · 2026-08-16