Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrading from 5.3.0 to 6.3.0 leads to many false positives

See original GitHub issue

Which version of lesshint are you using? 6.3.0

How are you running lesshint? CLI, Node.js API, Grunt/Gulp plugin? CLI

What’s your .lesshintrc configuration?

  "excludedFiles": [
  "idSelector": {
    "enabled": false
  "qualifyingElement": {
    "allowWithClass": true
  "spaceAroundComma": {
    "allowNewline": true
  "universalSelector": {
    "enabled": false
  "zeroUnit": {
    "style": "no_unit"

If you’re reporting a bug, please show us some code that’s failing.

All these lines below are failing to validate in the new version. Valid strings are being marked as unclosed and also the linter is linting comments in the file, which is really wrong.

@fontDroid: 'Droid Sans Mono', monospace;


// This is a comment (that contains some 'single quotes')


font-family: 'Lato-Regular';


// "This is a comment that contains double quotes, but there are an odd number per
//  line because we're including a quotation from somewhere else. lesshint treats it
//  incorrectly and marks the first line as a warning."

What did you expect to happen? lesshint should pass.

What’s the actual result? lesshint incorrectly marks these lines as warnings or errors.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

kaiyomacommented, Jan 24, 2019

I upgraded to 6.3.0 and everything looks good here. Thanks!

jwilssoncommented, Jan 24, 2019

This is fixed upstream so a fresh install of lesshint should solve this. If not, please let me know!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Upgrading from 6.2.X to 6.3.0 - Curity
It is recommended to have sliding windows enabled for these alarms, to reduce false positives for raised alarms. When it's deemed appropriate to...
Read more >
Changelog | Stylelint
Fixed: media-feature-parentheses-space-inside false negatives for multiple spaces (#4513). Fixed: selector-type-no-unknown false positives for SVG tags (#4495).
Read more >
Version history — Bio-Formats 6.11.1 documentation
refactored code to remove a false positive threat report in Fortinet. DICOM. fixed handling of some datasets with multiple optical paths.
Read more >
FortiSIEM 6.2.0 Online Help (PDF) - Amazon AWS
Need to Re-Configure Open Tunnel After Upgrade/Install of 6.3.0 ... Consequences of Running the IPS False Positive Test.
Read more >
other.xml.gz - PacketFence
I can't decide whether it's a real problem or false positives. ... for new ganglia - BuildRequire static version of iproute (#967214) -...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found