Skip to content
This repository has been archived by the owner on Mar 18, 2019. It is now read-only.

Make it more visible that cssnext is a plugin pack / a preset #251

Closed
MoOx opened this issue Jan 21, 2016 · 5 comments
Closed

Make it more visible that cssnext is a plugin pack / a preset #251

MoOx opened this issue Jan 21, 2016 · 5 comments
Labels
type: enhancement

Comments

@MoOx
Copy link
Owner

MoOx commented Jan 21, 2016

Should we use "plugin pack" or "preset" like Babel? poke @ai
MoOx added a commit to postcss/postcss that referenced this issue Jan 21, 2016
@MoOx
Add a note in README about cssnext including autoprefixer
6783303 
This is a common mistake.
Also, MoOx/postcss-cssnext#251
@MoOx MoOx mentioned this issue Jan 21, 2016
Merged
@ai
Copy link

ai commented Jan 21, 2016

Plugin pack is a simplier and cleaner word for preset. But preset is more popular. So I have no idea.

@jednano
Copy link
Contributor

jednano commented Jan 21, 2016

I prefer "plugin pack" because it's more clear what's going on. Preset could mean a number of different things.

@stevenvachon
Copy link

How about

cssnext is a plugin pack (or "preset")…

@piotr-cz
Copy link

piotr-cz commented Jan 4, 2017 •
edited

Another word used in php world is metapackage.
But anything would be helpful

@MoOx
Copy link
Owner Author

MoOx commented May 29, 2018 •
edited

postcss-cssnext has been deprecated in favor of postcss-preset-env. Read more at https://moox.io/blog/deprecating-cssnext/

@MoOx MoOx closed this as completed May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ai @MoOx @stevenvachon @piotr-cz @jednano