Reply To: [Solved] CSS modules and global scope

[shaneisme]

I suppose it depends on your goals.

If your new modules are going to be used in many projects, each with different definitions of their own .wrap, you might want to be more explicit. But that’s assuming your module is just that: a small module.

If these modules are only going to be used in a single project, or a few that have the same definition of .wrap, using a global class like that is exactly what you want to do.

It’s only when you want to make sure your module does the same thing no matter what’s going on around it that you want to get out of the global ‘scope’ by adding on a prefix or something.