twin.macro should support a zero-runtime solution

[NateRadebaugh]

To get the most out of my app, I'd like a zero-runtime solution for my CSS. Is this possible with twin.macro? Both styled-components and emotion have a non-zero runtime size.

[ben-rogerson]

A zero runtime is on the roadmap, it's something that I'll be exploring soon enough 👍

[ben-rogerson]

what I'd aim for is output to a css/sass file, but it's going to be tricky as there's a css prop/css import involved that twin doesn't have control over.

[NateRadebaugh]

Maybe it would be simpler to inject an interop for an existing zero-runtime static css lib like linaria or astroturf?

• https://github.com/callstack/linaria
• https://github.com/4Catalyzer/astroturf

[ben-rogerson]

Yeah great ideas here, fits in well with the existing idea of twin being the "glue" between different libs

[NateRadebaugh]

I'm not sure how best to test the integrations, I imagine we'll need another example in the twin.examples repo to validate e2e, but I've got a draft PR here in case this is a direction you want to go in for this:

• Add initial support for linaria for static CSS interop #248