cb() never called

[njueyupeng]

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\16070145\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'md5',
1 verbose cli '--save' ]
2 info using npm@6.0.1
3 info using node@v8.11.1
4 verbose npm-session 5fca2a4676dd1710
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 timing npm Completed in 4554ms
8 error cb() never called!
9 error This is an error with npm itself. Please report this error at:
10 error https://github.com/npm/npm/issues

[jsg2021]

Just ran into this. For me, this happens on node 10.1.0, but not 10.0.0.
Both npm 6.0.0, and 6.0.1 behave the same.

[jsg2021]

Actually, its starting to happen on all versions of node and npm 6.0.x

[jsg2021]

Seems machine dependent. :/

[jsg2021]

When its doing this, it doesn't write the log to disk. :/

[jsg2021]

Down grading to 5.6.0 works around it.
But on a completely separate machine npm(5.8.0-6.0.1) doesn't error with cp never called. :/

[anuj0877]

I am getting the same issue , My system configuration is:
node : v8.11.2
npm: 6.0.0
yarn: 1.6.0

I have also change the drive for Nodejs and now installed it on D rive but same issue occur. I have also attached my log file, Please check this.
2018-05-22T11_12_43_661Z-debug.log

I am trying to install reactjs but it return error , Here are my code:

D:\reactJS>npm install create-react-app -g
C:\Users\Anuj Sharma\AppData\Roaming\npm\create-react-app -> C:\Users\Anuj Sharma\AppData\Roaming\npm\node_modules\create-react-app\index.js
+ create-react-app@1.5.2
updated 1 package in 13.987s

D:\reactJS>create-react-app my-app

Creating a new React app in D:\reactJS\my-app.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...

yarn add v1.6.0
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/term-size/-/term-size-1.2.0.tgz: EPERM: operation not permitted, open 'C:\\Users\\Anuj Sharma\\AppData\\Local\\Yarn\\Cache\\v1\
pm-term-size-1.2.0-458b83887f288fc56d6fffbfad262e26638efa69\\vendor\\windows\\term-size.exe'".
info If you think this is a bug, please open a bug report with the information provided in "D:\\reactJS\\my-app\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.
  yarnpkg add --exact react react-dom react-scripts --cwd D:\reactJS\my-app has failed.

Deleting generated file... package.json
Deleting generated file... yarn-error.log
Deleting my-app / from D:\reactJS
Done.

[anuj0877]

I have also use this code:

D:\reactJS>create-react-app dashboard --use-npm

Creating a new React app in D:\reactJS\dashboard.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Anuj Sharma\AppData\Roaming\npm-cache\_logs\2018-05-22T11_12_43_661Z-debug.log

Aborting installation.
  npm install --save --save-exact --loglevel error react react-dom react-scripts has failed.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting dashboard / from D:\reactJS
Done.

[judas-christ]

I just got this error when running npm install --production on a node:8-alpine docker image on Google Cloud Container Builder. Tried building locally and it worked. Restarted the build on GCP without making any changes and it worked too. Slightly disconcerting.

[senseysensor]

the same here.
package.json: https://gist.github.com/senseysensor/38449c5748885f53bd320f41a66ca48b

output:

$ npm install --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'install',
npm verb cli   '--loglevel',
npm verb cli   'verbose' ]
npm info using npm@6.0.1
npm info using node@v6.14.0
npm verb npm-session 3221fff0ae168180
npm info lifecycle functions@~preinstall: functions@
npm timing stage:loadCurrentTree Completed in 30ms
npm timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
npm timing stage:loadIdealTree:loadShrinkwrap Completed in 886ms
npm timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 71ms
npm timing stage:loadIdealTree Completed in 1492ms
npm timing stage:generateActionsToTake Completed in 1108ms
npm verb correctMkdir /Users/serge/.npm/_locks correctMkdir not in flight; initializing
npm verb lock using /Users/serge/.npm/_locks/staging-575eb3cb7276c6f7.lock for /Users/serge/Web/Projects/servolab-node/functions/node_modules/.staging
npm timing audit compress Completed in 474ms
npm info audit Submitting payload of 60661bytes
npm timing audit submit Completed in 1818ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 1817ms
npm timing audit body Completed in 2ms
npm timing action:extract Completed in 8457ms
npm timing action:finalize Completed in 1602ms
npm timing npm Completed in 17480ms
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm 6.0.1 (the same was with 6.0). 5.7 works great. node 6.14. os x

[dariddler]

I had the same problem running node 10.1, npm 5.6, npm cache clean --force did the trick for me, not sure how "self-healing" the cache really is :)

[jsg2021]

cleaning the cache didn't fix it for me the other day.

[zohaib055]

I just ran into this issue on godaddy vps on local it works fine but on live it does not work

[andybarron]

I have this same issue. Downgrading to 5.6.0 "fixed" it. Also not producing any logs when I get this error.

[anuj0877]

I have also fix this issue, The was in Firewall permission and settings

…

On Thu, May 31, 2018 at 11:56 PM, Andy Barron ***@***.***> wrote: I have this same issue. Downgrading to 5.6.0 "fixed" it. Also not producing any logs when I get this error. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#20692 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlsKrkGFi3XcCkXCSedWvsmYcs0C6Zw9ks5t4DXsgaJpZM4UGmh7> .

[senseysensor]

why close? I still have the issue, it is always reproducable

[senseysensor]

which details do you need? I would share. By the way, if run npm install on already installed modules, there is no error. Only if remove node_modules/ and then try to install from scratch.

[zohaib055]

I just used these two commands and all worked again as well

npm config rm proxy
npm config rm https-proxy