Planning: inline critical CSS

[davidtheclark]

In dotcom we have a little system that parses static HTML with Cheerio, then uses PostCSS to and document.querySelector to create a CSS file that only contains selectors that match something on the page.

Because it's pretty slow, we split it across available processes.

I ran across an npm module with the same Cheerio-based system: https://github.com/tscanlin/css-razor. We could try using and contributing to that public module, instead of keeping our own. The code isn't super complicated, so I think it's perfectly fine to keep our own. But do we want to contribute to that project? @tristen what do you think?

[tristen]

You're probably well past this now but I'm a little confused by the title. You want to replace this with css-razor? Makes sense to me! What would need to be contributed to that project to get it to work for our needs? and how does this relate to inlining critical CSS?

[davidtheclark]

@tristen: Actually I made https://github.com/mapbox/css-sieve for this.