+1

from postcss-cssnext.

+1

from postcss-cssnext.

If for example vars are implemented before other functions we will face a real problem because we won't be able to add fallbacks for new functions without hardcoded values.
custom props are important deal.

Maybe we should act more like a huge fallback instead of "just" a replacement?

from postcss-cssnext.

FYI, custom props & calc have a preserve options to keep original code & just prepend fallbacks. We can add the same behavior for every features.

from postcss-cssnext.

This option will only make sense for low simple standalone features that cannot affect the entire stylesheet (eg: all functions & stuff like rebeccapurple).
Vars will always be a major feature since if you disable it (imagine it's supported in your browser scope) you will still have color(var(--blah)...) that we wont be able to resolve.

That being said, I'll still try to implement that for some features when it can be done. This will need to be clear in the documentation.

Will investigate about reusing what autoprefixer is using to make a standalone module that will be integrated here.

from postcss-cssnext.

That also a reason why I think cssnext should be like autoprefixer: adding code instead of doing some brutal replacement.
Anyone have opinion about that approach?

from postcss-cssnext.

FYI, here is a start from @Nyalab
https://github.com/Nyalab/caniuse-api
And here is something that would make us happy Nyalab/caniuse-api#3

from postcss-cssnext.

For now @Nyalab package is doing the opposite of what we want.

I think from this issue we will have something interesting soon
postcss/autoprefixer#284

from postcss-cssnext.

browserslist & caniuse-api are ready. Will integrate that asap.
Thanks @ai & @Nyalab for thoses modules.

from postcss-cssnext.

this will be awesome when you will have integrated those tools, keep up the good work man!

from postcss-cssnext.

YOU FEEL 1.0.0, DO YOU?

from postcss-cssnext.

FYI, this is done and ready.
But I need to fix this issue Nyalab/caniuse-api#18 in order to have a browserify build that works (for the playground).

from postcss-cssnext.

I take care of that very soon 😸

from postcss-cssnext.