-
Notifications
You must be signed in to change notification settings - Fork 348
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
Remove dependency on postcss #267
Conversation
}) | ||
|
||
value = csstree.generate(ast).slice(name.length + 1); | ||
value = value.slice(0, value.length - 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may want to extract 302-317 to a function. Similar to filterCss
except that it could not return the new value
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
csstree appears to still be in alpha, how stable is it? This module is a production dependency of a lot of projects.
From their readme:
npm reports 8 million downloads a month for this package and it is depended on by these packages (including SVGO and CSSO). |
I can write additional tests if you think that's required. |
This has been rolled back for now (1.19.3), pending further examination of #269, please take a look. Thanks! |
postcss
is a pretty heavy weight dependency if it is only being used for parsing an AST.Replaced with css-tree.