Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Better autoprefixer

See original GitHub issue

We’re using Glamor’s one which is fine but requires us to mangle our css-properties into { cssProperties } and back, as well as track mutations in the object and inject more postCSS nodes. What I’d like is to translate the rules that Glamor uses (which itself is vendored from https://www.npmjs.com/package/auto-prefixer) or, preferably, inline-style-prefixer/static into simple PostCSS instructions.

For the record, if there was a way to cut down postcss/autoprefixer to be small enough to include as part of Styled Components, that’d be fine too.

Issue Analytics

State:
Created 7 years ago
Comments:20 (11 by maintainers)

Top GitHub Comments

7reactions

mxstbrcommented, Oct 18, 2016

But in other hand, with in-browser tool you will not be able to work in prerender case, when you don’t know a browser.

Radium has you pass the user-agent for out-of-browser auto prefixing

I’m not too fussed about just adding all reasonable prefixes no matter the browser.

Sure, it doesn’t help, but instead of having three hundred lines of logic to determine which prefixes to add based on a user agent string I’d much rather just inject thirty lines of unnecessary CSS.

4reactions

mxstbrcommented, Nov 20, 2016

We now use inline-style-prefixer (as of #208 being merged, not yet released), can we close this @geelen?