Brad Cornes
Brad Cornes
@DevanB It’s already released under the `next` tag 📦
I'm not at my computer right now, but here's a couple of things to check: 1. Are you definitely on the latest version? I think it was `v1.0.0-alpha-5` 2. What...
Ah, good point. Maybe we can just add `inherits: require('@babel/plugin-syntax-object-rest-spread')`? https://github.com/jamiebuilds/babel-handbook/blob/master/translations/en/plugin-handbook.md#-enabling-syntax-in-plugins
Hey @muhajirframe There are a few notable differences: - using a custom Tailwind config is much easier with this plugin - as far as I can tell with the other...
The two plugins have fundamentally different approaches. The other one takes a compiled Tailwind CSS file and creates a list of class names from that, whereas this plugin does not...
No plans to support plugins right now. Not sure how feasible it is. Since you’re in CSS-in-JS-land anyway, you can write your own "plugins" in JavaScript, or use something like...
Thinking about it some more, I think it might be doable! I will have a look when I get chance.
Should be able to support something like this: **In** ```js import tw from 'tailwind.macro' let Header = tw.button` uppercase ${props => props.size === 'large' ? tw`text-lg` : tw`text-sm`} ` ```...
> It would be useful to use it to extend [...] You can do this already in pretty much the same way you would with standard `emotion`/`styled-components`: ```js import tw...
@schrapel are you still seeing this on `v1.0.0-alpha.5`?