-
Notifications
You must be signed in to change notification settings - Fork 458
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
TypeError: ast.remove is not a function #501
Comments
I get the following similar error:
node v7.10.0 |
Same error here
|
Similar error when running [email protected] as an exec command with ant. Like @thenewvu, no error with version 3.1.7:
My env:
|
Getting error in Atom Beautify 0.29.26 which uses CSS Comb. How to resolve?
|
Temporary workaround: Remove |
Is it this line of code that is failing? |
Is nobody maintaining this? |
@janwerkhoven I do maintain this repository. I will look into this asap. |
Should this https://github.com/csscomb/csscomb.js/blob/dev/src/options/block-indent.js#L48
not be
|
I am having the same issue and changing |
@ryanbowden It works! Thanks. |
The fix from @mfeckie worked for me. |
Still having this issue in the current version until I make the change @ryanbowden suggested. |
Still having issue, @ryanbowden update does'nt work with me :( |
Found the issues, cause my style has many lines commented out by |
I can confirm both the fix and work-around. How to avoid the errorsIn the Thanks @ryanbowden How to fix itIn Thanks @mfeckie ! |
Also getting similar error. Node v.8.9.1 & OS High Sierra with latest CSSComb. |
similar error .hoge {
$arr: (
"s": 3,
"m": 4,
"l": 5,
) !default;
@each $key, $value in $arr {
"&--of3" { // ← this is bad
}
}
}
Node: v8.7.0 |
Thanks, both fixes work! |
@ryanbowden ,It works for me too! |
My issue was this last asterisk which was preventing my code to run. Check if you don't have such syntax error because I have tried all the solutions above, but ended up to be that! UPDATED: watch out for unset comments, if you don't wrap them like this:
|
Fixed by @janwerkhoven with #552. |
🙌 |
Sir, I've met this error with all CSS files and with both custom and default configure:
This error only occurs in v4.0.1, not with v3.1.7.
My environment:
The text was updated successfully, but these errors were encountered: