An object of CSS properties that don't accept values with units
92
Quality
Pending
Does it follow best practices?
Impact
92%
0.92xAverage score across 7 eval scenarios
Style Object Processing
Import @emotion/unitless
100%
100%
Unitless property lookup
100%
100%
Unit addition logic
100%
100%
Zero value handling
100%
100%
Object iteration
100%
100%
Output format
100%
100%
Unitless Property Lookup
Import unitless object
100%
100%
Property lookup logic
100%
100%
Conditional unit addition
100%
100%
Zero value handling
100%
100%
Unitless property handling
100%
100%
Style object processing
100%
100%
Performance-Optimized Lookups
Import unitless
100%
100%
Direct lookup
100%
100%
Correct value check
100%
100%
Custom property handling
100%
100%
Zero value handling
100%
100%
Type checking
100%
100%
Correct unit application
100%
100%
Property Categories Coverage
Import unitless object
100%
100%
Unitless property lookup
100%
100%
Flexbox properties handling
100%
100%
Grid properties handling
100%
100%
Typography properties handling
100%
100%
Opacity properties handling
100%
100%
Layout properties unit addition
100%
100%
Z-index and order handling
100%
100%
Animation properties handling
100%
100%
Aspect ratio handling
100%
100%
Type-Safe Property Checking
Import unitless object
100%
100%
Type guard implementation
100%
20%
Unitless lookup usage
85%
50%
Type narrowing application
93%
0%
Property checking patterns
100%
100%
Conditional logic with unitless
100%
66%
Custom Property Handling Integration
Import unitless
100%
100%
Unitless property check
92%
92%
Custom property detection
100%
96%
Logic precedence
100%
100%
Zero value handling
100%
100%
Unit addition
100%
100%
Unit Addition Logic Support
Imports unitless package
100%
100%
Uses unitless object
100%
100%
Property lookup logic
100%
100%
Conditional unit addition
100%
100%
Handles numeric values
100%
100%
Zero value handling
100%
100%
Install with Tessl CLI
npx tessl i tessl/npm-emotion--unitless