add useful options section in readme #22
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I thought it may be helpful to add a "useful loader options" section to this demo. In a project of mine, I found the
camelCasequery param very helpful. It allowed me to keep dashes in my css class names and camel cased variables in my javascript.The problem was that it took me some time to figure out how to accomplish this. I traced it back from css-modules, to this demo, to css-loader (related PR there: https://github.com/webpack/css-loader/pull/242/files). So I was hoping to spare future css-modules users the time by pointing them in the right direction here.