how can you get globals on the exported object?

I don’t see why globals can’t be exported just like locals, thereby giving you a consistent API in your components, i.e. so you don’t have to juggle between using keys on a styles object and className strings.

[madyankin]

@faceyspacey @axyz Released in 3.1.0 https://github.com/css-modules/postcss-modules#exporting-globals

[madyankin]

I think I can take a look In a couple of days

On 4 Jun 2020, at 17:56, Andrea Moretti [e-mail] wrote:

@outpunk can you point us to what part of the code filters out globals? (not sure if it is in this repo or some css-modules nested dependencies).

This would be useful for my use case in https://github.com/utilitycss/atomic as I use the keys in the json to delete rules that are not exported (e.g. whole css files coming from ICSS imports and composes) (https://github.com/utilitycss/atomic/blob/master/src/postcss/remove-unused-electrons.ts)

I was thinking that I can parse the CSS and look for :global(.myClass) instances with a regexp and include them in the custom getJSON as “myClass”: “myClass”, but that sounds like a dirty solution and would be better to not remove them in the first place.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.