cssnext v2 roadmap (BREAKING CHANGES are welcome)

[MoOx]

Drop you ideas here if you are thinking about some breaking changes !

• get rid of the simple api that can return a string OR an object depending on your config in favor or the async api cssnext(config).process(input[, runtimeOptions]) offered by PostCSS 4.2+

Do not hesitate to drop anything here, there is no bad ideas, only ideas ;)

[klaemo]

fixing file watching would be nice

[topaxi]

Not a big one but will the process method return a promise?

[ben-eb]

@topaxi It supports both sync and async usage.

postcss/postcss@86eeb0c

[topaxi]

@ben-eb nice! :)

[jonathanong]

yeah i really need watching. it's embarrassing to recommend cssnext to coworkers when watching doesn't even work.

[MoOx]

@jonathanong @klaemo watcher issue is the next thing on my todo list. Except a patch soon.

[MoOx]

Closing for now since I am not even sure this project will make sense in a near future.
Related:

• 6.0 babel/babel#2168
• Common configs postcss/postcss#477