Ben Rogerson

Sometimes babel caching gets in the way, in Next you may need to break the cache sometimes by: - stop the dev server - remove the `.next` folder - start...

@Mldamico Assuming tailwindcss and twin are using the same tailwind.config, that sounds like a configuration issue. Please test with the latest `rc`: ```shell npm i twin.macro@rc ```

v3 has some new de-caching features - feel free to reopen if there's still issues

Hey there I took a look into this and yeah there's definitely an issue here. Seems the [token aware values](https://stitches.dev/docs/styling#token-aware-values) aren't working unless importing directly from stitches (while calling their...

Thanks for the reply @peduarte 👍 Here's the transformation that happens with twin: ```js import { styled } from "twin.macro"; const Button = styled("button", { backgroundColor: "$gray400", // Doesn't work...

Closing due to lack of activity

Thought I'd give this a test in the latest versions and seems like it's working great: ```json "@stitches/react": "^1.2.8" "twin.macro": "^3.0.0" ``` ```js import tw, { styled } from 'twin.macro'...

thanks for the PR's, you got a good base ready this feature - 🤞 it can be done!

I have given this a quick initial test with the `styled` import (and by including the fix from #256). This is working: ```js import tw from 'twin.macro' import { styled...

I'm keen to explore this further, but I've got quite a bit on my plate at the moment so I'll have to circle back around and tackle it 👍