Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

cssnext v2 roadmap (BREAKING CHANGES are welcome) #185

Closed
MoOx opened this issue Jul 16, 2015 · 7 comments
Closed

cssnext v2 roadmap (BREAKING CHANGES are welcome) #185

MoOx opened this issue Jul 16, 2015 · 7 comments

Comments

@MoOx
Copy link
Owner

MoOx commented Jul 16, 2015

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
Copy link

klaemo commented Jul 18, 2015

fixing file watching would be nice

@topaxi
Copy link

topaxi commented Jul 18, 2015

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

@ben-eb
Copy link
Contributor

ben-eb commented Jul 18, 2015

@topaxi It supports both sync and async usage.

postcss/postcss@86eeb0c

@topaxi
Copy link

topaxi commented Jul 18, 2015

@ben-eb nice! :)

@jonathanong
Copy link

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

@MoOx
Copy link
Owner Author

MoOx commented Jul 20, 2015

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

@MoOx
Copy link
Owner Author

MoOx commented Aug 6, 2015

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

@MoOx MoOx closed this as completed Aug 6, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants