Styled-components: Bundlesize and runtime postCSS

[drcmda]

We're attempting to finally sort out our styles and styled-components looks good. But the bundle size is very large, bigger than the UI components framework we're using even. Looking over the source it appears like it's shipping postCSS for runtime parsing which is unfortunate.

Csjs, styled-jsx and a couple of others allow for this to happen compile-time via Babel (for instance babel-plugin-csjs-postcss) with zero added bulk or cpu consumption. I know @mxstbr stance on postCSS but would it be OK if it's limited to the basic needs of styled-comps, basically allowing users to offload the work that's now being handled runtime to Babel?

[k15a]

In v2 we are switching from PostCSS to Stylis which will cut the bundle size in half. I don't know if there is much more we could improve to shrink the bundle size more.

[kitten]

@k15a @drcmda there's another thing on the to do list that will slightly improve runtime performance and shrink the bundle size even more, which will hopefully land in v2: CSS preprocessing.

I'm currently working on a preprocessor that processes the css in our babel plugin and thus eliminates the need for stylis, if you opt in.

[drcmda]

Thanks a lot @k15a , that's more than i could have hoped for!

@philpl Awesome! Normally we have about zero use for a runtime parser even if it's just a couple of kb and until now it was the only thing keeping us worried.