Add support for custom css modules name patterns #180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #156.
This adds support for custom patterns for generating names in css modules. Using
cssModules: true
continues to use the same default pattern as before, but you can also now set it to a config object:The currently supported segments are:
[name]
- the base name of the file name being transformed, without the extension[hash]
- a hash of the full file path[local]
- the original class nameWe could add more if needed as well. The pattern is parsed ahead of time and interpreted when writing out class names. Hopefully this solves the majority of use cases. We could add a JS callback for this as well, but it would add a lot of performance overhead so I would like to avoid it if possible.