Hello.


For illustrating purpose I post my workspace structure below:


Workspace/packages/main-theme [package type: theme]
|-- ...
|-- sass
|--etc
|--src
|--var
|-- ...

Workspace/packages/moduleA [package type: code]
|-- ...
|-- sass
|--etc
|--src
|--var
|-- ...


"moduleA" is a package of the type "code" and requires "main-theme". Styling definitions of "moduleA" are only located in "moduleA/sass/src" and "moduleA/sass/var" folders, not in "sass/etc".
For the package styling of "moduleA" I need to access the variables declared in "main-theme/sass/etc" what works fine.


The Problem is: The current output of the build process includes the styling definitions of "main-theme/sass/etc" too.
But I don't need them because they are always overwriting css definitions I already made in the "main-theme" thru the cascade.
I only want the additional styling rules for the "moduleA" in its moduleA.css without css rules of the "main-theme".


Is there a way to prevent including the "main-theme/sass/etc" style definitions into the moduleA.css?