Closed ukaaa closed 7 years ago
Can you reliably reproduce this? What command are you executing (e.g. apm install linter-js-standard
)?
This issue has been reported multiple times, but the last response was a year ago.
Could you link to those issues?
Yes I'm using apm install linter-js-standard
to reproduce this error.
The issues I found are for Windows though, and it was said to be fixed in Atom beta or in a newer Atom release. I'm not sure if that's the same for Ubuntu?
The other issues are not the same as this one. The minimatch
line is just a deprecation warning (already updated on master
) and should not cause the cb() never called!
error. However, I have found a similar issue on the Atom forum (unfortunately, unanswered).
Please check if ~/.atom/packages/linter-js-standard
already exists and remove it, if so. Then, try apm install linter-js-standard
again.
If this didn’t work, please try:
cd ~/.atom/packages
rm -rf linter-js-standard && mkdir linter-js-standard && cd linter-js-standard
curl -L https://github.com/ricardofbarros/linter-js-standard/archive/v3.9.3.tar.gz | tar xzf - --strip 1
npm install
This will download linter-js-standard directly from GitHub and install any dependencies using your own npm version. While this is not a solution, I’m interested if this workaround works.
Downloading it straight from GitHub works @sonicdoe! I still get the deprecation warning but not the “cb() never called” error. The linter is now present in Atom and working.
OK. Thanks for your time @sonicdoe, I found it was difficult to judge how relevant this issue was.
The same is happening to me with all Javascript linters. I always get "npm ERR! cb() never called!". I am using Ubuntu 17.10, by the way.
This issue has been reported multiple times, but the last response was a year ago. I have this same issue today on Ubuntu.
Not sure if this is related to the issue, but: