-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A way to control extension of CSS Modules. #14
Comments
This is the standard for CSS modules, but if you want to, create a PR with a custom option. Just make sure the default one is |
@martonlederer not all apps use this standard, so even though this is the standard I don't think it hurts to make it configurable. Does it? |
As I said, I have no problems with making it configurable
|
@martonlederer sorry my bad I did read your message too quickly. Here is a PR for it #34 |
make module file configurable #14
Right now there is no way to control how the plugin decides if a file should be treated as a module, cause regexp for that is hard-coded as
/\.module/
.If I want to use any of my css/sass files as a module, I have to name them all as
*.module.css
.Do you think we can make this configurable?
The text was updated successfully, but these errors were encountered: