Error running CSSLint

[shillem]

I'm using atom 1.19.
When linting any css file I get the error mentioned in the subject.
The console reads:

[Linter] Error running CSSLint Error: (node:75225) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: processFile(...).then is not a function
(node:75225) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at ChildProcess.<anonymous> (/Users/shillem/.atom/packages/linter-csslint/node_modules/sb-exec/lib/index.js:56:20)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:885:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

[thecrazyhare]

Hi, I'm running the same version of Atom and I am having the same issues.

[Arcanemagus]

I think I'm just going to completely remove the ability to lint on changes and switch this package to executing csslint as an external process on file saves. This will also allow switching to the official build which is necessary as nobody has stepped up to take over maintaining this package or the fork of csslint that it depends on (since csslint hasn't merged support for stdin text themselves...).

[dertin]

Same

[Linter] Error running CSSLint Error: (node:10115) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: processFile(...).then is not a function
(node:10115) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at ChildProcess.<anonymous> (/Users/gcespedes/.atom/packages/linter-csslint/node_modules/sb-exec/lib/index.js:56:20)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:885:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

[eddvq]

Having the same issues too.

[bdsexton]

I have been running into this error too—every time I preview, open, modify, or save a CSS file. It happens whether I modify CSS rules or comments.

× ∞

I am running Atom 1.19.0 x64 on macOS Sierra 10.12.6. I have not checked any other versions or operating systems.

[Arcanemagus]

This is a known issue, please stop posting "me too". The potential solutions are outlined in my earlier comment. If somebody wants to work on a PR for that I would be happy to review it, otherwise I will try to get to it sometime tomorrow.

I would highly recommend you switch to using stylelint (linter-stylelint) as CSSLint has been essentially abandoned.

[bdsexton]

@Arcanemagus People have just been trying to help by confirming that the issue is not isolated and by providing potentially relevant details. There is no need for discourtesy.

[Arcanemagus]

Would you like to become a maintainer here to help take care of issues and maintain the package? This package hasn't had an active maintainer in a very long time and it would be great if somebody who actually uses this provider and could give it the attention it deserves would take it on.

[jsejcksn]

@bdsexton I agree that most people are probably doing just as you described, but it contributes to noise due to the redundancy, requiring more effort from anyone trying to skim for actual information.

Most people are probably just unaware that they can use reactions to vote and that they can subcribe to issues without commenting.

Now, the reason(s) that they might be unaware... might deserve a more intense emotional reaction.

@Arcanemagus How spot on am I?

[Arcanemagus]

@jsejcksn Very spot on, thank you 😉.

[vnt]

I have the same problem:

[Linter] Error running CSSLint
See Console for more info. (Open View -> Developer -> Toggle Developer Tools)

I am running Atom 1.19.0 x64 on macOS Sierra 10.12.6.

[mingjunyang]

same too problem.

Atom    : 1.19.2
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0


├── linter@2.2.0
├── linter-csslint@1.3.4

error info

[Linter] Error running CSSLint Error: (node:11408) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: processFile(...).then is not a function
(node:11408) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    at ChildProcess.<anonymous> ($HOME/.atom/packages/linter-csslint/node_modules/sb-exec/lib/index.js:56)
    at emitTwo (events.js:106)
    at ChildProcess.emit (events.js:191)
    at maybeClose (internal/child_process.js:885)
    at Socket.<anonymous> (internal/child_process.js:334)
    at emitOne (events.js:96)
    at Socket.emit (events.js:188)
    at Pipe._handle.close [as _onclose] (net.js:501)
(anonymous) @ linter-registry.js [sm]:137

[bdsexton]

@Arcanemagus: Thank you for the stylelint and linter-stylelint recommendations. They seem great.

[Arcanemagus]

Well unfortunately it looks like nobody is interested in taking on maintenance of this package, so I'm going to have to move forward with the plan of removing support for linting on changes by switching this package back to using the master csslint fork. Hopefully will have a fix up in a bit!

[abstractmachines]

Thanks for your work @Arcanemagus

[samguergen]

I want to completely uninstall csslint. Remove this error message and just forget about the whole thing. How do I do that? I ran npm uninstall csslint but it doesn't work

[Arcanemagus]

@samguergen Since you are commenting on an issue in a repository for an Atom package, I'm going to assume you are using Atom and have linter-csslint installed. You can uninstall that from within Atom's Settings under the Packages section, or by typing apm uninstall linter-csslint in a terminal.