Add support for removing original classnames when using camelCase=true/'dashes'

[kumarharsh]

Do you want to request a feature or report a bug?
Feature Request

What is the current behavior?
CSS with both original and camelized classnames are retained in the final output.

If this is a feature request, what is motivation or use case for changing the behavior?
Would it be possible to introduce yet another flag which removes the uncamelized versions from the final output? I'm asking because of a comment on one of the issues: clinyong/vscode-css-modules#3 (comment)

Basically, by retaining both the camelized and original versions of a classname, the bundle size increases, sometimes by a lot for larger projects. If all developers are in with the syntax, perhaps it'd not be as problematic to remove the original classnames? Two extra options can be added to the camelCase options: camelCase: only and camelCase: dashesOnly which cause the plugin to not output the original classes. What do you think of the idea?

I'd be happy to make a PR if the team decides it's worthwhile to add to the loader.

[michael-ciniawsky]

@kumarharsh Should be fixed by #420

[joscha]

@michael-ciniawsky: #420 only removes duplicates, not the original classes. What @kumarharsh is suggesting makes total sense, but would be a breaking change. For this we'd need an additional flag. Happy to open a PR after #420 is merged.

[michael-ciniawsky]

@joscha kk I see, thx for joining in. Since we are working towards a next major (ES2015 Modules) etc. that isn't really a blocker as long as it makes things easier and general sense 😛

[joscha]

@michael-ciniawsky happy for me to open a PR for this? Should I add an additional flag, e.g. ?removeOriginal or ?replaceOriginal or do you want me to make the PR so it is a breaking change?

[michael-ciniawsky]

@joscha Personally I would prefer to make it a breaking change and avoid an extra flag, v1.0.0 will be a larger refactor anyways. For now we could maybe expose this behaviour as an option but please add a comment to refactor that later 😛 and not sure if we should do that at all tbh (confusion) .

cc @bebraw @d3viant0ne

[kumarharsh]

We can add camelCase: only and camelCase: dashesOnly if backward compatibility needs to be maintained.

[joscha]

Opened #445 @michael-ciniawsky and followed @kumarharsh's suggestion and made it an option.