What gets checked

The recommended preset runs Gameface-specific rules on top of normal HTML and CSS parsing. Below is what you can expect in day-to-day work—not every possible rule, but the main categories.

Stylesheets (.css, .scss)

• CSS properties Gameface does not support
• Partial support (for example only some keyword values work)
• Unsupported functions such as clamp() or min() where Gameface reports them as missing
• Selectors and pseudos that are unsupported or only partially supported
• Documented limits: var() / calc() inside @keyframes, var() with a fallback argument, calc() mixing % with px and similar units
• SVG-related animation rules in CSS (units in keyframes, stroke dash on non-path elements, and similar)

SCSS files are parsed in a tolerant mode so Sass variables and nesting do not block the run; lines that still use unresolved $variables may skip some value checks.

HTML (.html)

• Tags Gameface parses but does not implement (for example some form and table elements, depending on configuration)
• Partially supported elements when you use attributes Gameface does not handle
• data-bind-* spelling, {{ }} syntax, bind-for, class toggles, and model paths
• CSS inside <style> blocks and style="..." attributes—the same unsupported property/function/selector checks as in .css files
• SVG inside HTML: disallowed elements, mask/clip conflicts, stroke dash on wrong shapes

JSX and TSX (.jsx, .tsx)

• The same data binding checks as HTML on your components
• Inline style — both forms are linted, in different ways:
  • style={{ … }} — unsupported property names and partial values on object keys (for example style={{ alignContent: 'stretch' }})
  • style="..." / style={'...'} — full CSS text, including unsupported functions, keyframes limits, and SVG keyframe rules
• SVG trees in components

See Rules reference — JSX style props for which rules apply to object vs string styles.

JavaScript and TypeScript (.js, .jsx, .ts, .tsx)

• References to globals Gameface does not provide (for example some browser APIs)
• Partial APIs where only some members exist (reported as warnings by default)

Checks are static: dynamic property access and patterns ESLint cannot see without type information may not be reported.

What is not checked (today)

• Standalone .svg asset files (only SVG inside HTML/JSX)
• Every browser CSS feature—only what Gameface documents as unsupported or partial
• Runtime binding errors—only syntax and known unsupported features

For every rule id, default severity, and how to change them, see Rules reference.