Skip to content
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

Move to PostCSS #140

Open
ai opened this issue Dec 29, 2015 · 0 comments
Open

Move to PostCSS #140

ai opened this issue Dec 29, 2015 · 0 comments

Comments

@ai
Copy link

ai commented Dec 29, 2015

Right now Stylestats uses Rework CSS parser. But PostCSS CSS arser may be better:

  1. It is 1.4 times faster.
  2. It is much stable. For example, we uses integration tests with GitHub, Twitter and BrowserHacks CSS.
  3. It has different parsers too. Like postcss-safe-parser for legacy CSS with syntax errors or postcss-scss.
  4. It has bigger user base, so you will have better support and faster fixes.
@t32k t32k added this to the v7.0.0 milestone Jan 16, 2016
@t32k t32k removed this from the v7.0.0 milestone Nov 9, 2016
@t32k t32k added this to the v8.0.0 Release milestone Jan 4, 2017
@t32k t32k self-assigned this Jan 4, 2017
@t32k t32k removed their assignment Apr 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants