Every error and warning reported by morph check and morph build has a stable
rule code starting with mx-. When a diagnostic fires, the terminal shows the
code, what went wrong, a hint, a code frame, and a Learn more link that
opens the matching page in this reference:
error : mx-tag : Unknown tag <vidio>
hint: Did you mean <video>?
Learn more: https://morph.levizr.com/docs/errors/mx-tagmx-* code from your terminal output..mx files to native C++, so browser-only patterns cannot pass
through), shows the broken code, the fixed code, and how to tune the rule.morph build and dev-mode reloads until fixed. Warnings are
reported and never block — but they describe real bugs (missing key,
stub elements), so fix them too.Pages marked (rule) document a real constraint that morph check does not
report yet — violations surface as build failures or silently ignored code
instead of a labeled diagnostic. The cause and fix on those pages still apply
when you hit the underlying problem. Only implemented, triggerable checks are
listed here: there is no page for a feature that does not exist.
Severity is per-code with a documented default (see
lint configuration). You can turn a
rule off or change its severity in morph.config.json:
{
"lint": {
"disable": ["mx-list-key"],
"severities": { "mx-tag-stub": "error" }
}
}windowConfig keywindowConfig value type<img> without srckey used outside a listclass and className used togetherCSS.load() is deprecated'morph'morphState outside a componentmorphShared not at exported module scopemorphEvent not at exported module scopemorphState not destructured as pairmorphEffect first argument is not a functionkey