Skip to main content
VelinStyle v1.4.0
⌂ Home

What VelinStyle does not automatically migrate 1.4.0

Unresolved and Warning tokens stay in the report. The CLI never silently invents mappings for these categories. Deutsch

CategoryExamplesWhy
Statehover:, focus:, group-hover:, disabled:No State engine in 1.4.x
Darkdark:dark: ≠ Velin themes
Arbitraryw-[280px], h-[calc(...)]No arbitrary engine
Dynamic / cn()className={cn(...)}Counted as DynamicAttrsSkipped only
Proseprose, prose-zincTypography plugin domain
High-risk motiontransition-all, rotate-*, scale-*Semantic risk
Gradient directionbg-gradient-to-rHigh-risk / incomplete parity
Blurblur-xlHigh-risk
Fractionsleft-1/2, -translate-x-1/2High-risk
Theme roles without Core targetbg-card, text-muted-foregroundOut of scope / no invent
Palette without Core targettext-purple-500Honest unresolved
2xl2xl:px-4Breakpoint not supported
grid-cols-15Outside Compat scale
Non-utility markersgroup, peer, toasterNot utility Compat

Because these categories stay unresolved, the static 80% gate is not reached. Pilot reference: 69.4% Mapped (559/806). Realistic static ceiling without new State / Arbitrary / Theme / Dynamic engines: about 70–71%.

Migration Intelligence: Theme/State/Palette/Half-Step/Dim/Typo residuals stay without auto targets. Catalog entries = 0 · SAFE_REWRITE = 0. See Migration Intelligence.

Full migrate workflow: Tailwind migrate. Package: @birdapi/velinstyle-tailwind. Overview: 1.4.0 Release Overview.