Skip to content

/ suit

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kill preprocessor #162

Open
simonsmith opened this issue Feb 13, 2019 · 2 comments
Open

Kill preprocessor #162

simonsmith opened this issue Feb 13, 2019 · 2 comments

Comments

@simonsmith
Copy link
Member

@simonsmith simonsmith commented Feb 13, 2019

Most of the features in there have native browser support already, and it's very easy to hook up postcss-cli otherwise.

Either that or we could create a plugin pack, similar to this.
@simonsmith simonsmith mentioned this issue Feb 13, 2019
Open
@giuseppeg
Copy link
Member

@giuseppeg giuseppeg commented Feb 13, 2019

+1 for creating the preset
@mlnmln
Copy link
Contributor

@mlnmln mlnmln commented Mar 1, 2019 •
edited

Agreed. From a consumers' perspective it's more transparent to depend on a preset.

Edit: We should either create a plugin pack or consider just adopting postcss-preset-env https://github.com/csstools/postcss-preset-env. Which would stay true to the "future facing CSS" paradigm, would'n it?
@mlnmln mlnmln mentioned this issue Mar 1, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@simonsmith @giuseppeg @mlnmln
You can’t perform that action at this time.