Node.js-specific utilities and runtime functionality for Tailwind CSS v4, providing compilation tools, module dependency analysis, source map handling, path normalization, and optimization utilities.
43
Pending
Does it follow best practices?
Impact
43%
1.16xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
Design system loader (__unstable__loadDesignSystem)
Loader usage
0%
14%
Base option
50%
50%
Import resolution
25%
0%
Token mapping
0%
0%
Ordering fidelity
70%
50%
Module and stylesheet resolution with custom resolvers
Custom JS resolver
0%
71%
Default fallback
50%
100%
Stylesheet resolver
0%
0%
Dependency callbacks
66%
80%
Tailwind CSS compilation helpers (compile/compileAst)
String compile
100%
100%
AST compile
0%
60%
Dependency capture
100%
100%
URL rewrite toggle
0%
53%
Root reporting
0%
20%
Output parity
50%
50%
Cross-platform path normalization
Library import
100%
100%
normalize usage
44%
77%
UNC handling
50%
75%
Canonical output
66%
100%
No custom normalizer
20%
30%
DEBUG environment flag parsing
env import
0%
0%
Pattern handling
0%
0%
Override parsing
0%
0%
Truthiness
0%
0%
CSS URL rewriting for asset paths
Rewrite API
0%
0%
Base and root
20%
40%
Image-set support
0%
40%
Skip external/data
66%
33%
Async result
0%
0%
Performance instrumentation with hierarchical timers
Instrumentation setup
0%
0%
Nested timers
0%
0%
Async timing
0%
0%
Hit counters
0%
0%
Reporting & disposal
0%
0%
Reset behavior
0%
0%
Require/ESM cache busting utilities
Require clearing
100%
100%
ESM loader hook
0%
0%
ESM refresh
50%
50%
Path handling
100%
100%
CSS optimization with Lightning CSS and source map fixes
Optimize call
100%
100%
Range fix
100%
100%
Source map chain
50%
100%
Warnings surfaced
0%
10%
Source map serialization utilities
String input via toSourceMap
80%
80%
Decoded map serialization
100%
0%
Missing source handling
50%
0%
Inline comment usage
80%
46%
Direct package dependency
100%
46%