★ Convergence with PostCSS (make cssnext a preset, a la Babel 6.0)

[MoOx]

Following the move of Babel 6.0, we should thinking to:

• move part of cssnext interface into postcss core
• think about how to make cssnext more like an easy preset so people can choose what they want.
• make postcss-cssnext

[awayken]

😢 Reading this makes me sad, but as long as there is a neat and (fairly) easy way to convert existing cssnext sites to whatever is next for the project, then I'm up for it.

[awayken]

As a preset, would cssnext become something like postcss-cssnext?

[MoOx]

Be reassured, I won't kill the baby. Whatever solution is choosen, this will be easy to do for everyone, with a clear CHANGELOG on what to do.
I can see 2 things indeed:

• create postcss-cssnext and encourage the usage
• maybe keep "cssnext" package for a while that is basically what cssnext is today, probably with some changes under the hood, but not for end user.

That said, I think the most important thing will be to kill cssnext wrappers (gulp, grunt etc) and encourage postcss wrapper with the use of postcss-cssnext. It's not nice to have to maintain 2 similar things.
.postcssrc is required before any transition is planned, to help people having an easy transition without any pain.

[MoOx]

In short, you should be happy that we will work on something better for everyone ;)

[awayken]

That's good to hear. I still really love the ideas behind cssnext, so I'm glad there are the beginnings of a plan.

[magsout]

I think the idea of babel is interesting. It remains modular, eco-system is consistent and everything goes in the right direction. I like the idea. 👍

[magsout]

Just a question. cssnext is not just a wrapper module, there is still a sense. How all this can be found in this version of postcss-cssnext?

[MoOx]

Something like postcss-cssnext will just be a bundle of cssnext "features" (no options). Some details about my idea here #202 (comment)
I hope the other things that cssnext brings (easy interface, cli etc) will be backported to postcss, that the idea behind this issue. But I guess nobody is excited about it...

[magsout]

But I guess nobody is excited about it...

Maybe because this idea is more philosophical. Currently cssnext works very well and make a awesome job. It is easy to install (npm) and to use (webpack, grunt, gulp). The subtlety of what you want to do isn't necessarily pertinante at beginning.

[MoOx]

postcss-cssnext is almost ready. That will help.