How to remove dependency on another file?

The project suggests that the user will be able to change the design of the blocks without editing the core of the module. That’s how it works on IMPORT. Simple and understandable, as in any programming language.

##### You can edit files
// design1.scss
$a: red;

// design2.scss
$a: green;

// style.scss 
@import 'design1';
// or
// @import 'design2';

@import 'core';


##### You can not edit
// core.scss
.d { color: $a }

With using USE, it is necessary to explicitly prescribe a module with variables in the core of the module. This creates dependence on another file and does not allow them to manage.

# You can edit files #
// style.scss 
@use 'design1';
// or
// @use 'design2';

@use 'core';


# You can not edit #
// core.scss
@use 'design1' as design; // !!! incorrect - depends on another file !!!

.d { color: design.$a }

How to make the user change the design only in the style.scss file? Without editing the core.scss file.

[maxsite]

The problem is that IMPORT does not interfere with anyone and works without any problems. USE creates its scope that is not always needed by developers. In other programming languages, if you need an area of ​​visibility, it sets where it is in demand.

The main goal is convenience for users. For example, in my projects there are more than 50 variables that are easily overlapped through the IMPORT in two lines of code. With USE is impossible to do this.

Maybe you should consider the opinion of those who use Sass in their projects? And not to close inconvenient ticket? If you really want modularity in Sass, it may be worth making instructions for a global scope as it works now?

Sorry for GoogleTranslate

[sKopheK]

hi, got stuck with scoped @imports and also am not sure about migrating bourbon library