The Sass Blog offers  guides, tutorials, and updates on Sass, a popular CSS preprocessor used for front-end web development. From basic Sass syntax to advanced techniques and best practices, the Sass Blog equips web developers with the knowledge and tools needed to streamline their stylesheet authoring process and create more maintainable and scalable CSS codebases.

Sass

The `@import` rule in Sass is officially deprecated as of Dart Sass 1.80.0, to be fully removed by Dart Sass 3.0.0. Developers are encouraged to migrate to the module system using `@use` and `@forward`, which offer better maintainability and avoid CSS duplication. Tools and commands are provided to silence deprecation warnings or treat `@import` as an error to facilitate the transition.

Sass: `@import` is Deprecated

Controlling Deprecation Warnings Controlling Deprecation Warnings permalink

Built-in Functions Built-in Functions permalink

Well this is just plain stu*id…
My pipeline lives on top of a scss file that’s like:
@tailwind base;
@tailwind components;
@tailwind utilities;
// Variables, Functions and Mixins
<a href="https://app.daily.dev/import" data-mention-id="IQVt4AejeUqaHQcdXtczw" data-mention-username="import">@import</a> “config/config”;
<ul>
<li>a bunch of other imports… I tried to change those to @use and it just screws my cascade because now i have tailwind defined stuff after my overrides, without even getting started about the infinity of “repeated” namespaces from plugin imports…</li>
</ul>
this is hell.