Nick Aspinall
Nick Aspinall
@oliviertassinari Thanks, I've spent a few minutes generating a [minimal reproduction of the issue here](https://github.com/nijk/babel-plugin-transform-react-remove-prop-types-issue-140). I may well be doing something wrong but here's what I found: 1. When using...
@oliviertassinari is that not the development version of React? The [production version](https://unpkg.com/[email protected]/umd/react.production.min.js) doesn't attempt to access `process.env`.
Sorry, ignore that - I've just re-read the file you linked to
I'm just catching up on this as I've noticed some issues with CSS specificity although in a slightly different context. I can see why there is a consideration for using...
Actually I may have worked it out; AFAICT from the docs `::stylefy/with-classes` should be able to solve "simple" specificity use cases like the one that @jiangts cites in the original...
@Jarzka Are you sure that this is necessary given my comment above? I believe that the `::stylefy/with-classes` approach should work if it is used correctly. I haven't tested it but...
Sorry, my bad - I thought it added those classes to the selector chain in the CSS. So going back to your idea, I'm assuming that the scope `(stylefy/init {:scope...
I can't think of a better way if I'm honest
I think so, it's a real edge case
Agreed, and further convenience wrappers can be provided by wrapping the component in an HOC that does a lot of the hard work for you, e.g. `[with-style [:a {...} "click...