-
Notifications
You must be signed in to change notification settings - Fork 15
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
Don't print CSS parsing errors to stderr #1
Comments
Thanks for catching this. It'll be fixed asap.
Apparently, the performance benefits of skipping css and js processing are overstated |
This has been fixed. Update your grabity version and it should be fine. |
Thanks a lot for so fast fix! |
Output (stderr):
I don't understand yet why this module requires
jsdom
(I expect it could just parse an HTML file with other tools, rather than using jsdom which also tries to parse CSS and so on).The text was updated successfully, but these errors were encountered: