Fetching documentation…
Severity: warning | Blocks morph build: no
Status: documented rule —
morph checkdoes not report this code yet. The underlying problem still breaks your build or your UI; the cause and fix below apply when you hit it.
A token in className does not resolve to any Tailwind utility Morph knows:
warning : mx-tailwind-class : Unknown Tailwind class `flxe`
hint: Did you mean `flex`? See the 500+ supported utilities
Learn more: https://morph.levizr.com/docs/errors/mx-tailwind-classThis is a warning: the build proceeds, the unknown token is ignored, and the element loses that piece of styling.
Morph resolves Tailwind classes at compile time to native style values —
there is no Tailwind runtime in the binary. A token with no mapping compiles to
nothing, so a typo (flxe, bg-red-999) silently drops styling. The warning
carries a suggestion because the intended class is usually one edit away. No
Node.js or Tailwind install is involved — the resolver is built into the
compiler (see Tailwind support).
// ⚠️ `flxe` resolves to nothing — mx-tailwind-class
export default function App() {
return <div className="flxe items-center">Hello</div>;
}// ✅ Correct utility name
export default function App() {
return <div className="flex items-center">Hello</div>;
}When the class genuinely does not exist in Morph's set:
style or a CSS file rule instead.Steps:
style or CSS.morph check.{
"lint": {
"disable": ["mx-tailwind-class"]
}
}Escalate instead if dropped utilities keep slipping through review:
{
"lint": {
"severities": { "mx-tailwind-class": "error" }
}
}