-
Notifications
You must be signed in to change notification settings - Fork 130
Automation of enabling/disabling features like autoprefixer #94
Comments
Would be nice to ideate a bit on the syntax to make it cleaner feeling, since things like |
Indeed. |
@ianstormtaylor You don't like "Internet Explorer" being transformed to "Explorer" right ? |
@ianstormtaylor we can fix grammar issues in Autoprefixer too to have common API. |
@MoOx Issue is only in |
We should definitly make a common module to ask caniuse-db for a reponse. |
@ai not sure, we should check all possibilities you have :) |
@MoOx yeap, common module will be nice. But there is one problem. |
BTW, there are also awesome Autopolyfiller, which need browser selection too. /cc @azproduction |
What about including request feature directly to caniuse-db ? |
@MoOx now |
|
/cc @Fyrd |
I've contacted @wuchengwei to see if we can get the npm name :) |
@azproduction I remember, that you ask for some separated browser selector, for quieries like |
Used to control autoprefixer and the splitCssIfIeLimitIsReached transform. Removes support for --autoprefix (autoprefixer is now used if and only if --browsers is specified) Currently requires autoprefixer to be available. Keeping an eye on segmentio/myth#94
Like autoprefixer we could use caniuse-db with a list of browsers to know what features to use or not.
This is not essential now, but it will became when browser start to implement all features we got here.
We need to check @ai works :)
The text was updated successfully, but these errors were encountered: