> In the documentation for the first one, it describes a default "file scope", but really no definition of what a file is. Probably because if you don't know

> In the documentation for the first one, it describes a default "file scope", but really no definition of what a file is. Probably because if you don't know what a file is, you have a lot more you need to learn first. It's a bare basic fundamental that goes way beyond CSS. But scope is true - CSS Modules like to pretend the CSS is specific to where it's used, and gloss over that some css attributes cascade to all children. @scope, and specifically the lower bound part of @scope, would fix this.