Migrating Sass from @import to @use and @forward
Replace deprecated Sass @import with Dart Sass modules using @use and @forward, plus explicit namespaces and CI validation.
Loading…
ReadMeFeed / Community knowledge
#dart-sass
Real questions. Useful conversations. Find the people who know your stack.
sassModern Sass Architecture with @use and Built‑in Modules
Learn how Sass’s @use rule eliminates duplicate output and global namespace clashes by loading modules once under an explicit namespace, with a concrete migration example and verification steps.
Stop duplicating CSS with Sass @use and @forward
Replace @import with Sass modules to scope variables, deduplicate compiled CSS, and expose a single library entry point.
Migrate Sass stylesheets from @import to @use and @forward
Replace deprecated Sass @import with the @use and @forward module system to stop namespace collisions and prepare for removal.
Sass Mixins vs Functions: Architecture Notes for Design System Tokens
Separate Sass logic from output: use functions for values and mixins for CSS, behind the @use module system.
Replace Sass @import with @use and @forward in Dart Sass
Migrate Dart Sass stylesheets from deprecated @import to the @use/@forward module system without duplicating CSS or breaking global tokens.
Migrating Sass Stylesheets from @import to the Module System
Learn how to replace Sass @import with the module system (@use/@forward) to avoid duplicate CSS, global namespace pollution, and name collisions, with a concrete migration example and verification steps.
Sass @use: Namespaces, Single-Load Semantics, and Theming a Component Library
Sass's @use module system replaces @import with namespaced, load-once modules and a with() configuration API. Here's how to structure a themeable library and what migration costs.
Moving Beyond @import: Managing Sass Dependencies with @use and @forward
Stop fighting global variable collisions in Sass. Learn how to use @use and @forward in Dart Sass to create namespaced, maintainable style architectures.