Skip to content

Conversation

@halfzebra
Copy link
Contributor

@halfzebra halfzebra commented Aug 3, 2018

I have replaced the mentions of postcss-cssnext with postcss-preset-env since cssnext is deprecated.

Type

  • Docs

SemVer

  • Bug (:label: Patch)

Issues

Checklist

  • Lint and unit tests pass with my changes
  • I have added tests that prove my fix is effective/works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes are merged and published in downstream modules

@michael-ciniawsky michael-ciniawsky changed the title Replace postcss-cssnext with postcss-preset-env in the README.md docs(README): replace postcss-cssnext with postcss-preset-env Aug 3, 2018
Copy link
Member

@michael-ciniawsky michael-ciniawsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@halfzebra Thx 🙇

@halfzebra
Copy link
Contributor Author

Thanks for merging this, I'm wondering if it would make sense to remove autoprefixer from examples featuring postcss-preset-env, because it has autoprefixer already?

@michael-ciniawsky
Copy link
Member

🤔 We could remove all current references to autoprefixer and add a autoprefixing example to the examples section instead with a note/warning for postcss-preset-env users about that matter.

### `Autoprefixing`

\```js
// ...example
\```

> :warning: `postcss-preset-env` already includes the autoprefixer plugin.... and so forth

@michael-ciniawsky michael-ciniawsky removed this from the 3.1.0 milestone Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace cssnext with postcss-preset-env

2 participants