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

MoOx · 2015-09-01T19:05:30Z

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 · 2015-09-03T15:07:39Z

😢 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 · 2015-09-03T15:08:29Z

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

MoOx · 2015-09-03T15:15:26Z

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 · 2015-09-03T15:16:34Z

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

awayken · 2015-09-03T15:30:04Z

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 · 2015-09-08T05:07:02Z

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 · 2015-09-08T05:08:12Z

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 · 2015-09-08T05:12:53Z

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 · 2015-09-08T05:34:51Z

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 · 2015-09-10T06:22:10Z

postcss-cssnext is almost ready. That will help.

codemakerlive · 2015-09-10T11:31:38Z

Good work @MoOx, looking forward to it on npm

ben-eb · 2015-09-10T11:33:16Z

@MoOx Awesome. 👍

ChristopherBiscardi · 2015-09-16T02:25:46Z

+1 We are running into a situation where we have cssnext running with a few other plugins and it looks like postcss-cssnext could help make our config a bit neater.

FWIW, the cssnext CLI has helped when debugging in the past, but it doesn't seem like a necessity.

.postcssrc is interesting, because it could mean configuring css for a static site generator much like babel is configured, without the generator being opinionated beyond "processed with postcss".

MoOx · 2015-09-16T19:26:41Z

I plan to deprecate (and not update to cssnext v2) all runners:

cssnext-loader > postcss-loader + postcss-cssnext
gulp-cssnext > gulp-postcss + postcss-cssnext
grunt-cssnext > grunt-postcss+ postcss-cssnext
fly-cssnext > fly-postcss + postcss-cssnext
cssnextify > browserify-postcss + postcss-cssnext
duo-cssnext > duo-postcss + postcss-cssnext
cssnext-brunch > postcss-brunch + postcss-cssnext
broccoli-cssnext > broccoli-postcss + postcss-cssnext
cssnext-connect > postcss-middleware + postcss-cssnext

We should

deprecate those packages on npm with a message + link on how to migrate with ease (I will try to offer a nice changelog so people might understand why to migrate to postcss-cssnext)
move deprecated repos back to their owner or to postcss org ? (poke @ai)
move cssnext to postcss org and delete the cssnext org ?

Not sure if it's necessary if the things about the org is necessary, but I found it would be stupid to keep a useless org, merging with postcss seems a better idea.

poke @ai and @cssnext/owners: sounds good to you? Any objection/comment ?
I would like to get a response from each runner owner please :)

ai · 2015-09-16T19:27:39Z

I move depreacted repos to my account to clean org https://github.com/ai/autoprefixer-core

ai · 2015-09-16T19:28:21Z

I think cssnext org is great for cssnext plugins

MoOx · 2015-09-16T19:29:29Z

There is not such thing as cssnext plugin and I plan to deprecate runners, so the org will be empty (just one repo)

lionelB · 2015-09-16T19:36:06Z

Sounds good to me.
+1 for readme update to ensure a smooth transition

magsout · 2015-09-16T19:37:55Z

SGTM go 👍

ai · 2015-09-16T19:39:37Z

@MoOx in this case we can remove org :)

shinnn · 2015-09-16T19:40:18Z

Nice design 👍

watilde · 2015-09-16T19:42:14Z

Yeah sounds good to me too!
+1

MoOx · 2015-09-16T19:47:57Z

MoOx · 2015-10-03T08:05:00Z

Yep. Just check the differences in postcss-cssnext readme.

felixfbecker · 2015-10-15T17:59:16Z

I just want cssNext to be to Sass/Less/Stylus what babel is to CoffeeScript/TypeScript/...

MoOx · 2015-10-15T18:35:51Z

@felixbecker this issue has been raised because babel (in 6.0) is becoming an engine like postcss that will do nothing by default (no transformation if no plugins added). If we want to follow babel footstep we should make cssnext a postcss preset (like babel-preset-es2015). That's why I mentionned a possible chane for the name. I still want mire input from cssnext users about that.

felixfbecker · 2015-10-15T20:17:06Z

Imo you must keep the name cssnext. Babel may be switching to a module approach, but they keep the name and everyone knows it stands for using next ES's features. CssNext has this association too. PostCSS doesnt.

MoOx · 2015-10-15T20:38:31Z

No that my point. Babel won't focus on ES future in it's core. That's a fact (just look at babel development branch atm).
That's why I am not sure how to adapt cssnext to be "just a preset" to enable the future of css and promote postcss as a main tool (in order to avoid duplicate effort for gulp/grunt/whatever runners/cli etc...).

MoOx · 2015-12-29T06:15:53Z

FYI, work is in progress to make official the deprecation of cssnext in favor of postcss-cssnext.
In order to keep the cssnext history/issues, I am merging back postcss-cssnext work in this repo, will delete postcss-cssnext repo and rename cssnext repo to postcss-cssnext.
The website will be update accordingly to this major change and provide a page with information on how to easily upgrade (and why). When this will be ready, I will close this issue in favor of postcss/postcss#477

MoOx · 2015-12-29T06:16:49Z

After that all cssnext runners and interface will be deprecated on npm with a link in the deprecation message to point to the related (incoming) doc.

MoOx · 2016-01-03T19:02:07Z

Subscribers => #230 (comment)

MoOx · 2016-01-04T07:17:49Z

Currently deprecating all runners I can and giving repo back to their owners.

MoOx · 2016-01-04T07:30:30Z

I can successfully deprecate the following:

cssnext
cssnext-loader
gulp-cssnext
grunt-cssnext
duo-cssnext
cssnext-brunch
cssnext-connect
broccoli-cssnext

But I wasn't able for this packages

fly-cssnext
gobble-cssnext
cssnextify

@bucaran or @DrKraken, please run this command npm deprecate fly-cssnext "cssnext is now postcss-cssnext. fly-cssnext is deprecated. Use fly-postcss instead. See postcss-cssnext migration guide http://cssnext.io/postcss/"

@Swatinem, please run this command npm deprecate gobble-cssnext "cssnext is now postcss-cssnext. gobble-cssnext is deprecated. Use gobble-postcss instead. See postcss-cssnext migration guide http://cssnext.io/postcss/"

@ByteMuse, please run this command npm deprecate cssnextify "cssnext is now postcss-cssnext. cssnextify is deprecated. Use browserify-postcss instead. See postcss-cssnext migration guide http://cssnext.io/postcss/"

MoOx · 2016-01-04T07:51:32Z

I make transfert request to all original creators of the packages. Tell if I made something wrong.

ghost · 2016-01-04T07:51:53Z

Hi @MoOx

The amount of information is massive, do you have a FAQ or link to see a summary of what happened?

Thanks!

MoOx · 2016-01-04T07:53:59Z

It's very simple: http://cssnext.io/postcss/

ghost · 2016-01-04T07:55:22Z

Thanks, the JavaScript scene is so exciting 😆

MoOx · 2016-01-04T07:56:09Z

It's alive.

MoOx added type: enhancement status: help wanted status: discussion status: wip labels Sep 3, 2015

MoOx mentioned this issue Sep 7, 2015

Upgrade to postcss 5.x #202

Closed

MoOx removed the status: help wanted label Sep 10, 2015

MoOx mentioned this issue Sep 16, 2015

Update setup.md #215

Closed

This was referenced Oct 3, 2015

What's your favorite project on GitHub? MoOx/ama#4

Closed

Old version of cssnano using deprecated css-list #223

Closed

keithamus mentioned this issue Oct 13, 2015

Add mixins by new proposal #203

Closed

MoOx mentioned this issue Oct 15, 2015

Update pixrem dependency to v3.0.0 for rootValue #225

Closed

MoOx mentioned this issue Oct 19, 2015

cssnext doesn't work with PostCSS 5 #227

Closed

ben-eb mentioned this issue Oct 20, 2015

Update autoprefixer-core to the latest version to remove console warnings #229

Closed

MoOx mentioned this issue Oct 20, 2015

⚠︎ Deprecate cssnext in favor or postcss-cssnext #230

Closed

MoOx mentioned this issue Nov 10, 2015

Minify breaks calc() lionelB/cssnext-brunch#10

Closed

MoOx mentioned this issue Nov 25, 2015

Upgrade to PostCSS 5.x #209

Closed

MoOx mentioned this issue Dec 29, 2015

[WIP] postcss-cssnext merge #238

Merged

5 tasks

MoOx removed status: discussion status: wip labels Jan 4, 2016

MoOx closed this as completed Jan 4, 2016

shinnn mentioned this issue Jan 4, 2016

Parent file doesn't change when imported files change MoOx/broccoli-cssnext#2

Open

jwywr mentioned this issue Nov 2, 2016

Use "postcss-cssnext" instead of "cssnext" and other plugins SC5/sc5-styleguide#884

Open

Uh oh!

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

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

Comments

MoOx commented Sep 1, 2015

awayken commented Sep 3, 2015

Uh oh!

awayken commented Sep 3, 2015

Uh oh!

MoOx commented Sep 3, 2015

Uh oh!

MoOx commented Sep 3, 2015

Uh oh!

awayken commented Sep 3, 2015

Uh oh!

magsout commented Sep 8, 2015

Uh oh!

magsout commented Sep 8, 2015

Uh oh!

MoOx commented Sep 8, 2015

Uh oh!

magsout commented Sep 8, 2015

Uh oh!

MoOx commented Sep 10, 2015

Uh oh!

codemakerlive commented Sep 10, 2015

Uh oh!

ben-eb commented Sep 10, 2015

Uh oh!

ChristopherBiscardi commented Sep 16, 2015

Uh oh!

MoOx commented Sep 16, 2015

Uh oh!

ai commented Sep 16, 2015

Uh oh!

ai commented Sep 16, 2015

Uh oh!

MoOx commented Sep 16, 2015

Uh oh!

lionelB commented Sep 16, 2015

Uh oh!

magsout commented Sep 16, 2015

Uh oh!

ai commented Sep 16, 2015

Uh oh!

shinnn commented Sep 16, 2015

Uh oh!

watilde commented Sep 16, 2015

Uh oh!

MoOx commented Sep 16, 2015

Uh oh!

MoOx commented Oct 3, 2015

Uh oh!

felixfbecker commented Oct 15, 2015

Uh oh!

MoOx commented Oct 15, 2015

Uh oh!

felixfbecker commented Oct 15, 2015

Uh oh!

MoOx commented Oct 15, 2015

Uh oh!

MoOx commented Dec 29, 2015

Uh oh!

MoOx commented Dec 29, 2015

Uh oh!

MoOx commented Jan 3, 2016

Uh oh!

MoOx commented Jan 4, 2016

Uh oh!

MoOx commented Jan 4, 2016

Uh oh!

MoOx commented Jan 4, 2016

Uh oh!

ghost commented Jan 4, 2016

Uh oh!

MoOx commented Jan 4, 2016

Uh oh!

ghost commented Jan 4, 2016

Uh oh!

MoOx commented Jan 4, 2016