I did not trust the short package blurb so I read the actual Dusk lint files. The rules are stricter than the readme. @Dusk Network ships a Stylelint config for web CSS, version 1.0.6. It starts from standard Stylelint then locks house taste. Class names must be BEM. Nesting max is 4. Compound selectors max is 6. Extend is out. Initial is out. Border none is out. Transition all is out. Raw http or https in backgrounds is out. Todo and fixme in comments fail. Use named colors when they exist. Write alpha as a number. Empty blocks fail. Bad hex fails. Duplicate selectors fail. Browser support misses only warn.
Same shop has an ESLint config at version 4.0.1. JS rules are tight. No var. Strict equals. No console. Complexity cap 14. Depth 3. Five params max. Sort keys. Sort imports. Prettier runs last so format and lint do not argue. #dusk Network also has a Prettier package.
Three configs. One look. Almost nobody else depends on them. Stylelint last moved in 2024. That is the fact. This is their app style made public, not a popular standard. I like that they published the file instead of a slogan. I am skeptical of CSS rules that sit still for two years. Still, one shared style beats ten files that look random.
Use this only if you want their frontend limits. Read the config first. Override BEM or the complexity cap if it fights your stack. Keep lint boring. Spend the energy on the protocol.
$DUSK
Same shop has an ESLint config at version 4.0.1. JS rules are tight. No var. Strict equals. No console. Complexity cap 14. Depth 3. Five params max. Sort keys. Sort imports. Prettier runs last so format and lint do not argue. #dusk Network also has a Prettier package.
Three configs. One look. Almost nobody else depends on them. Stylelint last moved in 2024. That is the fact. This is their app style made public, not a popular standard. I like that they published the file instead of a slogan. I am skeptical of CSS rules that sit still for two years. Still, one shared style beats ten files that look random.
Use this only if you want their frontend limits. Read the config first. Override BEM or the complexity cap if it fights your stack. Keep lint boring. Spend the energy on the protocol.
$DUSK
