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

Outdated Autoprefixer #231

Closed
jojmaht opened this issue Oct 29, 2015 · 6 comments · Fixed by #238
Closed

Outdated Autoprefixer #231

jojmaht opened this issue Oct 29, 2015 · 6 comments · Fixed by #238

Comments

@jojmaht
Copy link

jojmaht commented Oct 29, 2015

When should we expect to see Autoprefixer upgraded to 6.0 in cssnext?
@magsout
Copy link
Contributor

magsout commented Oct 29, 2015

@skinnyfoetusboy #230 I guess never ?

@magsout
Copy link
Contributor

magsout commented Oct 29, 2015

@skinnyfoetusboy https://github.com/cssnext/postcss-cssnext with autoprefixer 6.0

@jojmaht
Copy link
Author

jojmaht commented Oct 29, 2015

Damn.

@jojmaht
Copy link
Author

jojmaht commented Oct 29, 2015

@MoOx Maybe you should update the README to reflect the change of direction you've chosen for cssnext?

@MoOx
Copy link
Owner

MoOx commented Oct 29, 2015

It will require some time to explain people how to migrate. This require some amount of time I am not ready to spend yet :/
I would like this issue postcss/postcss#477 to be handled before in order to make a "generic" transition easier for everyone.

@MoOx MoOx mentioned this issue Dec 29, 2015
Merged
5 tasks
@MoOx MoOx closed this as completed in #238 Jan 4, 2016
@MoOx
Copy link
Owner

MoOx commented Jan 4, 2016

Done in postcss-cssnext. cssnext is now postcss-cssnext. cssnext is deprecated. See postcss-cssnext migration guide http://cssnext.io/postcss/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] postcss-cssnext merge MoOx/postcss-cssnext
3 participants
@MoOx @magsout @jojmaht