LESS mixin and extend breaks CSSComb
See original GitHub issueTill recently I had no problem using CSSComb on LESS files in Sublime Text 2. Now, with ST3, I get an error on my LESS files. I have found that the error appears when I use a mixin with a negative number, like so .text-indent(-16px);
or an extend like so &:extend(._pill-button);
But I haven’t checked all my files to see if something else bothers CSSComb.
The error message is: /Users/ellen/Library/Application Support/Sublime Text 3/Packages/CSScomb JS/node_modules/csscomb/lib/csscomb.js:205 throw new Error('Parsing error at ’ + filename + ': ’ + e.message) ^ Error: Parsing error at undefined: Please check the validity of the CSS block starting from the line #15 at Object.Comb.processString (/Users/ellen/Library/Application Support/Sublime Text 3/Packages/CSScomb JS/node_modules/csscomb/lib/csscomb.js:205:19) at Socket.<anonymous> (/Users/ellen/Library/Application Support/Sublime Text 3/Packages/CSScomb JS/csscomb.js:23:37) at Socket.EventEmitter.emit (events.js:117:20) at _stream_readable.js:919:16 at process._tickCallback (node.js:419:13)
If I remove the offending line, or just the minus sign when that is the problem, it works fine
Ellen
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 9 years ago
- Reactions:3
- Comments:19 (1 by maintainers)
Top GitHub Comments
This is fixed in the latest csscomb release 🎉
This is still an issue, any idea of what is going on, or is this not going to be sorted or even a point in the a direction to look at ways to fix it