at-rule-no-unknown errors

I get at-rule-no-unknown errors for things like @extend, @mixin etc. with this plugin installed. I could be mistaken, but I assumed this plugin would cover those cases, but right now I have to use a custom ignore rule:

{
  "extends": [
    "stylelint-config-standard",
    "stylelint-config-css-modules"
  ],
  "plugins": [
    "stylelint-scss"
  ],
  "rules": {
    "at-rule-no-unknown": [ true, {
      ignoreAtRules: ['extend', 'at-root', 'debug', 'warn', 'error', 'if', 'else', 'for', 'each', 'while', 'mixin', 'include', 'content', 'return', 'function']
    }]
  }
}

[davidtheclark]

Another possibility would be to write a new rule for stylelint-scss that wraps at-rule-no-unknown but automatically ignores Sass’s special at-rules. Something like this:

var sassAtRules = [
  'extend', 'at-root', 'debug', 
  'warn', 'error', 'if', 'else', 
  'for', 'each', 'while', 'mixin', 
  'include', 'content', 'return', 'function'
];

function atRuleNoUnknownSassy(on, options) {
  return function (root, result) {
    const defaultedOptions = Object.assign({}, options, {
      ignoreAtRules: sassAtRules.concat(options.ignoreAtRules || [])
    });

    stylelint.rules['at-rule-no-unknown'](on, defaultedOptions)(root, result);
  };
};

This solution means your rule is easy to maintain, without duplicating code and at-rule lists in stylelint.

This ability to manually invoke stylelint rules within plugin rules opens a lot of doors!

[eriklharper]

@neverfox I’m in the same boat, but what I realized is that because stylelint-scss is a stylelint plugin, it doesn’t automatically enable any rule for you because that’s how plugins work.

What we really need to make the linter “scss aware” is a scss lint config that we can tell stylelint to extend instead, the same way you’re extending stylelint-config-css-modules above.

I did a quick search online for “stylelint scss config” but it isn’t turning up anything, perhaps this is a perfect moment for me to attempt to write one myself!