Cannot read property '0' of undefined #17858

OKNoah · 2017-07-19T19:14:28Z

I'm opening this issue because:

[✓] npm is crashing.
npm is producing an incorrect install.
npm is doing something I don't understand.
Other (see below for feature requests):

What's going wrong?

~/P/dreamer-api *master> npm install --save caminte
npm WARN eslint-config-airbnb@15.0.2 requires a peer of eslint-plugin-jsx-a11y@^5.1.1 but none was installed.
npm WARN eslint-config-airbnb@15.0.2 requires a peer of eslint-plugin-react@^7.1.0 but none was installed.
npm WARN dreamer-api@0.1.0 No repository field.

npm ERR! Cannot read property '0' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/noah/.npm/_logs/2017-07-19T19_09_33_702Z-debug.log

and

~/P/dreamer-api *master> npm remove --save sequelize
npm WARN eslint-config-airbnb@15.0.2 requires a peer of eslint-plugin-jsx-a11y@^5.1.1 but none was installed.
npm WARN eslint-config-airbnb@15.0.2 requires a peer of eslint-plugin-react@^7.1.0 but none was installed.
npm WARN dreamer-api@0.1.0 No repository field.

npm ERR! Cannot read property '0' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/noah/.npm/_logs/2017-07-19T19_11_35_695Z-debug.log

How can the CLI team reproduce the problem?

I do not know.

supporting information:

npm -v prints:

5.3.0

node -v prints:

v8.1.4

npm config get registry prints:

https://registry.npmjs.org/

Windows, OS X/macOS, or Linux?:

macOS

Network issues:
- [✓] None
Container:
- [✓] None

EDIT: Seems to only happen with node 8.1.4

The text was updated successfully, but these errors were encountered:

furagi · 2017-07-20T07:57:15Z

Happens to me too when I try to install chalk. Node version is 6.9.4, npm version is 5.3.0, log:

2468 verbose stack TypeError: Cannot read property '0' of undefined
2468 verbose stack     at rmStuff (/usr/lib64/node_modules/npm/lib/unbuild.js:61:24)
2468 verbose stack     at tryCatcher (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
2468 verbose stack     at ret (eval at makeNodePromisifiedEval (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:13:39)
2468 verbose stack     at lifecycle.then.then (/usr/lib64/node_modules/npm/lib/install/action/unbuild.js:12:12)
2468 verbose stack     at tryCatcher (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
2468 verbose stack     at Promise._settlePromiseFromHandler (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
2468 verbose stack     at Promise._settlePromise (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
2468 verbose stack     at Promise._settlePromise0 (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
2468 verbose stack     at Promise._settlePromises (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
2468 verbose stack     at Async._drainQueue (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
2468 verbose stack     at Async._drainQueues (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
2468 verbose stack     at Immediate.Async.drainQueues (/usr/lib64/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
2468 verbose stack     at runCallback (timers.js:649:20)
2468 verbose stack     at tryOnImmediate (timers.js:622:5)
2468 verbose stack     at processImmediate [as _immediateCallback] (timers.js:594:5)

jlchereau · 2017-07-20T08:15:28Z

npm 5.3.0 is broken (on windows 10) for me too after upgrading to nodeJS v8.2.0. Same symptoms/logs as described above. npm install -g npm@5.2.0 temporarily fixes the problem.

jpbecotte · 2017-07-21T17:13:28Z

@jlchereau : Thank you!

gabiap96 · 2017-07-23T07:13:13Z

@jlchereau i had the same error on mint and this worked

saeedtabrizi · 2017-07-23T11:38:06Z

Same problem with following configuration .

node : 8.2.1
npm : 5.3.0

refack · 2017-07-23T16:28:04Z

Same problem, but I have logs
2017-07-23T16_22_13_400Z-debug.zip
Reproducing repo
citgm-npm-bug.zip

And I think I know what I did "wrong":

git clone https://github.com/nodejs/citgm
npm i
npm i spawn-wrap - wanted to test it - it's not listed in package.json
git pull - that updated package.json
npm i - broken - can't even npm rm spawn-wrap

refack · 2017-07-23T16:30:49Z

P.S. node@8.1.3 & npm@5.3.0
rimrafing node_modules solves the problem.

drewpayment · 2017-07-24T03:05:35Z

Same issue here, but my config:

Node@7.7.4
NPM@5.3.0

Downgrading to NPM@5.2.0 worked perfectly for now.

jlchereau · 2017-07-24T08:38:57Z

@refack, from my experience rimrafing restores npm install but not npm update as long as any of the modules installed has been shrinkwrapped. In my solution, aws-sdk triggers the error. Restoring npm 5.2.0 is apparently the only way until we get a fix.

Saturate · 2017-07-24T08:55:45Z

Having the same issue with 5.3.0

4841 verbose stack TypeError: Cannot read property '0' of undefined
4841 verbose stack     at rmStuff (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\lib\unbuild.js:61:24)
4841 verbose stack     at tryCatcher (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
4841 verbose stack     at ret (eval at makeNodePromisifiedEval (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promisify.js:184:12), <anonymous>:13:39)
4841 verbose stack     at lifecycle.then.then (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\lib\install\action\unbuild.js:12:12)
4841 verbose stack     at tryCatcher (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
4841 verbose stack     at Promise._settlePromiseFromHandler (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:512:31)
4841 verbose stack     at Promise._settlePromise (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:569:18)
4841 verbose stack     at Promise._settlePromise0 (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:614:10)
4841 verbose stack     at Promise._settlePromises (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:693:18)
4841 verbose stack     at Async._drainQueue (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:133:16)
4841 verbose stack     at Async._drainQueues (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:143:10)
4841 verbose stack     at Immediate.Async.drainQueues (C:\Users\teamcity\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:17:14)
4841 verbose stack     at runCallback (timers.js:672:20)
4841 verbose stack     at tryOnImmediate (timers.js:645:5)
4841 verbose stack     at processImmediate [as _immediateCallback] (timers.js:617:5)
4842 verbose cwd C:\BuildAgent\work\57a4acfd1659de9f\www\Components\FK\Project\Design
4843 verbose Windows_NT 6.3.9600
4844 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\teamcity\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "i"
4845 verbose node v6.10.3
4846 verbose npm  v5.3.0
4847 error Cannot read property '0' of undefined
4848 verbose exit [ 1, true ]

dennyd · 2017-07-24T11:51:35Z

same issue with node 8.1.1, npm 5.3.0

Wandang · 2017-07-24T17:09:46Z

Same issue for me.

Config:
Node@v8.2.1
NPM@5.3.0

isaaczinda · 2017-07-24T18:35:00Z

Same issue for me. I'm at npm 5.3.0, node v8.2.1.

DevYukine · 2017-07-24T22:37:03Z

same for me npm 5.3.0 node v8.2.1

weegeekps · 2017-07-25T01:09:37Z

Same as the others. NPM 5.3.0 and Node v8.2.1

flubox · 2017-07-25T09:34:26Z

Same thing here, node@6.9.5 and NPM 5.3.0 won't work, but NPM 5.2.0

zontafil · 2017-07-25T10:03:09Z

same,
node 7.9.0, npm 5.3.0

jorrit · 2017-07-25T11:23:13Z

I think there are plenty of same here messages already.

Bejor · 2017-07-25T14:42:42Z

Same error for me.
Node 7.9.0, npm 5.3.0

Downgrading to 5.2 solves the issue

karlvaniseghem · 2017-07-25T20:02:11Z

same error for me
Node 8.1.2, npm 5.3.0

Downgrading npm to 5.2.0 solves the issue

CarrierDirectJoe · 2017-07-25T22:21:31Z

Same error for me
Node 6.11.1, npm 5.3.0

Downgrading npm to 5.2.0 solves the issue

damienleroux · 2017-07-26T07:59:44Z

same with v8.1.3 & npm@5.3.0.
Crash on npm i or npm prune.

Same error and same error stack

elizavetd · 2017-07-26T12:04:05Z

Same error for me
Node v8.2.1, npm v5.3.0

Downgrading npm to 5.2.0 solves the issue

Karolis92 · 2017-07-26T13:43:25Z

Same error...
Node v8.2.1, npm v5.3.0

Downgrading npm to 5.2.0 solves the issue

cullylarson · 2017-07-26T20:58:02Z

Same error with npm 5.3.0. Downgrading to 5.2.0 fixed it.

zhaoxiongfei · 2017-07-27T09:09:43Z

Same error with centos@6.5 & gcc@4.9.2 & node@8.2.1 & npm@5.3.0. Downgrading to 5.2.0 fixed it.

refack · 2017-07-27T14:39:18Z

@zkat, please say you'll into this... 🙏

SimonSchick · 2017-07-27T14:52:46Z

Also present on:

➜  ~ uname -a
Darwin XXXXXXXXXXX 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
➜  ~ node -v
v8.2.1
➜  ~ npm -v
5.3.0

howlettt · 2017-11-30T02:56:34Z

Sorry no, the repo is private and already fixed by removing the node_modules folder & reinstalling.
If I see it again I'll try to extract the relevant files to a public repo.

pb-uk · 2017-11-30T10:16:02Z

I was getting this after an upgrade to npm 5.5.1 but only on some projects - I realised it was those with only devDependencies.

I fixed it by adding an empty dependencies element to my package.json and then npm worked fine, so try this. Strangely though I haven't managed to reproduce the problem by deleting the dependencies element again!

tsofist · 2017-11-30T12:02:57Z

I'm over it
I have solved that issue by installing the Yarn

arackaf · 2017-11-30T15:59:18Z

@zkat there's some repro repo's way at the top of this thread - this one should work too

https://github.com/arackaf/booklist

I downgraded to npm 4 to work around it, but you should be able to use it to test if you're in need of test cases.

graphicelements · 2017-12-01T11:22:57Z

Same issue here with:
node v8.9.1
npm v5.5.1

Update!!!
This solution worked for me with Gulp:

Run npm rebuild node-sass
Remove node_modules and package-lock.json
Run npm install

AlexanderKositsyn · 2017-12-05T15:14:31Z

Was the same problem.
Solved it by typing:

npm rebuild node-sass
Remove node_modules and package-lock.json
npm init -y
copy-past the old package.json to the new package.json
and then install gulp-pug(pug was a problem that drop down the npm)

midik · 2017-12-05T18:12:22Z

I confirm that npm@latest does the trick for me:
node 9.2.0
npm 5.6.0

dennisjac · 2017-12-07T21:53:22Z

What is the situation here? I ran into the same issue and I'm seeing that the bug is open since July.
Given that npm is a critical part of todays javascript ecosystem it's a bit disconcerting the see this issue getting no attention.

NN--- · 2017-12-07T21:56:14Z

@dennisjac Have you tried everything above ? Like removing package-lock.json and installing all packages ?
Did you try 5.6.0 ? It should fix the problem. https://github.com/npm/npm/releases

zkat · 2017-12-07T21:59:16Z

@dennisjac the situation is that there's been multiple fixes related to this, and most people aren't running into it anymore, but there's a couple of folks still trickling in. Sometimes you have a variety of bugs and they all manifest with the same error. The most notorious is probably cb() not called, which is a reaaaally general one that doesn't tell us much.

riakharisma · 2017-12-08T01:05:41Z

Solved for me
win 10
node LTS 8.9.2
npm 5.6.0

dennisjac · 2017-12-08T01:06:00Z

The problem is that the first time i fixed things by nuking node_modules, package-lock.json and clearing the cache but now the problem has returned and now I'm thinking about writing a script that nukes everything every time before I do an npm install just to make builds reliable again.

How do I get npm version 5.6.0? I just installed node 8.9.2 but that still has 5.5.1 bundled it seems.

riakharisma · 2017-12-08T01:08:44Z

@dennisjac
npm i -g npm@next

zkat · 2017-12-08T07:02:26Z

Gonna close this, since it seems to be solved for people on 5.6.0

killroy42 · 2017-12-11T12:58:33Z

How do I get onto 5.6.0? I just get this error when I try to upgrade or downgrade in any way:
Error: Cannot find module '/tmp/npm.3077/package/bin/read-package-json.js'

smithdalec · 2017-12-11T14:16:46Z

Fixed with npm@5.6.0: npm i -g npm@latest
I also had to rm -rf node_modules and npm i from my project once after the npm upgrade. Subsequent installs do not have the error.

FlandersBurger · 2017-12-12T16:19:56Z

Downgrading to 5.2.0 and then upgrading to 5.6.0 right after worked for me.

zkat · 2017-12-12T20:30:59Z

since this seems to be resolved, I'm gonna lock it -- please open a new issue if you find yourself having this error again (and after making sure you've done the steps of clearing your node_modules/ and installing fresh and all that).

Thanks everyone for participating!

Fix: npm/npm#17858 Fix: npm/npm#18042 Fix: https://npm.community/t/issue-npm-dedupe-crash-with-typeerror-cannot-read-property-0-of-undefined/644/3 Close: #201 This fixes a bug where a package folder might have a package.json which is missing or lacks a name property. It also properly detects the scoped-ness of a package folder even if the package name is not scoped, since one might install `express@npm:@scope/express` and end up in that state.

robinhouston mentioned this issue Jul 24, 2017

Undefined pkg variable in node_modules\npm\lib\unbuild.js:62 #17865

Open

1 task

kenany added the npm5 label Jul 26, 2017

turnerguo mentioned this issue Nov 30, 2017

Cannot read property '0' while npm i turnerguo/notes#4

Open

jongb mentioned this issue Nov 30, 2017

Tools version setup/requirement vq-labs/vq-marketplace-web-app#25

Open

nicolasgramlich mentioned this issue Dec 4, 2017

💪 Typesafe pick, omit and pluck bluebirds-blue-jay/utils#1

Merged

zkat closed this as completed Dec 8, 2017

npm locked and limited conversation to collaborators Dec 12, 2017

Cannot read property '0' of undefined #17858

Cannot read property '0' of undefined #17858

Comments

OKNoah commented Jul 19, 2017 • edited

I'm opening this issue because:

What's going wrong?

How can the CLI team reproduce the problem?

supporting information:

furagi commented Jul 20, 2017

jlchereau commented Jul 20, 2017

jpbecotte commented Jul 21, 2017

gabiap96 commented Jul 23, 2017

saeedtabrizi commented Jul 23, 2017

refack commented Jul 23, 2017 • edited

refack commented Jul 23, 2017

drewpayment commented Jul 24, 2017

jlchereau commented Jul 24, 2017 • edited

Saturate commented Jul 24, 2017

dennyd commented Jul 24, 2017

Wandang commented Jul 24, 2017

isaaczinda commented Jul 24, 2017

DevYukine commented Jul 24, 2017

weegeekps commented Jul 25, 2017

flubox commented Jul 25, 2017

zontafil commented Jul 25, 2017

jorrit commented Jul 25, 2017

Bejor commented Jul 25, 2017 • edited

karlvaniseghem commented Jul 25, 2017

CarrierDirectJoe commented Jul 25, 2017

damienleroux commented Jul 26, 2017

elizavetd commented Jul 26, 2017

Karolis92 commented Jul 26, 2017

cullylarson commented Jul 26, 2017

zhaoxiongfei commented Jul 27, 2017 • edited

refack commented Jul 27, 2017

SimonSchick commented Jul 27, 2017

howlettt commented Nov 30, 2017

pb-uk commented Nov 30, 2017

tsofist commented Nov 30, 2017

arackaf commented Nov 30, 2017

graphicelements commented Dec 1, 2017 • edited

AlexanderKositsyn commented Dec 5, 2017 • edited

midik commented Dec 5, 2017

dennisjac commented Dec 7, 2017

NN--- commented Dec 7, 2017

zkat commented Dec 7, 2017

riakharisma commented Dec 8, 2017

dennisjac commented Dec 8, 2017

riakharisma commented Dec 8, 2017

zkat commented Dec 8, 2017

killroy42 commented Dec 11, 2017

smithdalec commented Dec 11, 2017 • edited

FlandersBurger commented Dec 12, 2017

zkat commented Dec 12, 2017

OKNoah commented Jul 19, 2017 •

edited

refack commented Jul 23, 2017 •

edited

jlchereau commented Jul 24, 2017 •

edited

Bejor commented Jul 25, 2017 •

edited

zhaoxiongfei commented Jul 27, 2017 •

edited

graphicelements commented Dec 1, 2017 •

edited

AlexanderKositsyn commented Dec 5, 2017 •

edited

smithdalec commented Dec 11, 2017 •

edited