Should This Config Include Sass Rules?

This config includes Sass rules, but we use the config in every project, even those that don't use Sass. This sometimes causes problems, like rules intended for Sass colliding is new native CSS features. Is there a better way to handle this? Can we scope the Sass rules to files with Sass extensions? What about Vue components with ``?

If it's not possible to scope based on Sass usage, should we consider dropping the Sass rules? We're using Sass less and less on new projects, but older projects that are still supported retain it. Maybe this config should split into two? The outcome of this issue should be to thoroughly investigate our options and make a recommendation about if and how to change this config.

Start by inspecting the shareable config's Sass rules and how consumers select them; compare behavior for Sass files, native CSS, and Vue components with lang="scss". Document whether file- or syntax-based scoping is supported, then recommend scoped rules, a split config, or removal based on compatibility.

Written by the indexing model from the issue text.