src/content/docs/linter/rules/use-qwik-classlist.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JSX and TSX" icon="seti:javascript"> ## Summary - Rule available since: `v2.1.4` - Diagnostic Category: [`lint/correctness/useQwikClasslist`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule doesn't have a fix. - The default severity of this rule is [**error**](/reference/diagnostics#error). - This rule belongs to the following domains: - [`qwik`](/linter/domains#qwik) - Sources: - Same as [`qwik/prefer-classlist`](https://qwik.dev/docs/advanced/eslint/#prefer-classlist){
"linter": {
"rules": {
"correctness": {
"useQwikClasslist": "error"
}
}
}
}
Prefer using the class prop as a classlist over the classnames helper.
This rule encourages the use of class prop which natively supports strings, objects, and arrays, enabling fine-grained reactivity and optimal performance. Using utilities like classnames can interfere with Qwik's reactivity model and prevent the framework from optimizing component updates. Prefer using the built-in class prop for best results.
For more information, see: Qwik documentation on class bindings
<div class={classnames({ active: true, disabled: false })} />
<div class={{ active: true, disabled: false }} />