ricardofbarros / linter-js-standard

Atom linter plugin for JavaScript, using JavaScript Standard Style
https://atom.io/packages/linter-js-standard
MIT License
99 stars 50 forks source link

Cannot install on Ubuntu due to npm error “cb() never called” #192

Closed ukaaa closed 7 years ago

ukaaa commented 7 years ago

This issue has been reported multiple times, but the last response was a year ago. I have this same issue today on Ubuntu.

npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm ERR! cb() never called!
➜ apm -v
apm  1.18.1
npm  3.10.10
node 6.9.5 x64
python 2.7.12
git 2.7.4

➜ node -v
v6.11.0

➜ npm -v
4.6.1

Not sure if this is related to the issue, but:

➜ npm ls minimatch -g
├─┬ commitizen@2.9.6
│ └─┬ glob@7.1.1
│   └── minimatch@3.0.4 
├─┬ gulp@3.9.1
│ └─┬ vinyl-fs@0.3.14
│   ├─┬ glob-stream@3.1.18
│   │ ├─┬ glob@4.5.3
│   │ │ └── minimatch@2.0.10  deduped
│   │ └── minimatch@2.0.10 
│   └─┬ glob-watcher@0.0.6
│     └─┬ gaze@0.5.2
│       └─┬ globule@0.1.0
│         ├─┬ glob@3.1.21
│         │ └── minimatch@0.2.14  deduped
│         └── minimatch@0.2.14 
└─┬ npm@4.6.1
  ├─┬ fstream-npm@1.2.0
  │ └─┬ fstream-ignore@1.0.5
  │   └── minimatch@3.0.3 
  ├─┬ glob@7.1.1
  │ └── minimatch@3.0.3 
  └─┬ node-gyp@3.6.0
    └── minimatch@3.0.3 
sonicdoe commented 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?

ukaaa commented 7 years ago

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?

sonicdoe commented 7 years ago

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.

ukaaa commented 7 years ago

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.

sonicdoe commented 7 years ago

Thanks, not the answer I was hoping for but the one I was expecting 😀

I’ll close this issue now since it doesn’t seem to be directly caused by linter-js-standard. Feel free to open an issue over at atom/atom or atom/apm.

ukaaa commented 7 years ago

OK. Thanks for your time @sonicdoe, I found it was difficult to judge how relevant this issue was.

usemoslinux commented 6 years ago

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.