npm@5 TypeError: Cannot read property 'version' of null #298

yvele · 2017-06-01T14:47:17Z

Looks like using npm 5 we have a problem.

package_json.version at line 262 is undefined and throws at line 270

TypeError: Cannot read property 'version' of null
    at Object.module.exports.evaluate (/Users/yvele/repo/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/versioning.js:270:32)
    at install (/Users/yvele/repo/node_modules/fsevents/node_modules/node-pre-gyp/lib/install.js:168:31)
    at Object.self.commands.(anonymous function) [as install] (/Users/yvele/repo/node_modules/fsevents/node_modules/node-pre-gyp/lib/node-pre-gyp.js:50:37)
    at run (/Users/yvele/repo/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp:79:30)
    at Object.<anonymous> (/Users/yvele/repo/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp:131:1)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)

Main NPM issue:

npm5 package-lock.json uses resolved URL for version property of existing node_modules npm/npm#16926

Related issues:

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

sgtcoolguy · 2017-06-02T16:54:11Z

I think this is due to npm5 using a URL value for the version property in package.json files now.

There's a hint in the full error output below:

> node-ios-device@1.3.1 install /Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device
> node-pre-gyp install --fallback-to-build

node-pre-gyp info it worked if it ends with ok
node-pre-gyp verb cli [ '/Users/cwilliams/.nvm/versions/node/v6.10.2/bin/node',
node-pre-gyp verb cli   '/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/.bin/node-pre-gyp',
node-pre-gyp verb cli   'install',
node-pre-gyp verb cli   '--fallback-to-build' ]
node-pre-gyp info using node-pre-gyp@https://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.6.34.tgz
node-pre-gyp info using node@6.10.2 | darwin | x64
node-pre-gyp verb command install []
node-pre-gyp ERR! install error 
node-pre-gyp ERR! stack TypeError: Cannot read property 'version' of null
node-pre-gyp ERR! stack     at Object.module.exports.evaluate (/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/node-pre-gyp/lib/util/versioning.js:270:32)
node-pre-gyp ERR! stack     at install (/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/node-pre-gyp/lib/install.js:168:31)
node-pre-gyp ERR! stack     at Object.self.commands.(anonymous function) [as install] (/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/node-pre-gyp/lib/node-pre-gyp.js:50:37)
node-pre-gyp ERR! stack     at run (/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/node-pre-gyp/bin/node-pre-gyp:79:30)
node-pre-gyp ERR! stack     at Object.<anonymous> (/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/node-pre-gyp/bin/node-pre-gyp:131:1)
node-pre-gyp ERR! stack     at Module._compile (module.js:570:32)
node-pre-gyp ERR! stack     at Object.Module._extensions..js (module.js:579:10)
node-pre-gyp ERR! stack     at Module.load (module.js:487:32)
node-pre-gyp ERR! stack     at tryModuleLoad (module.js:446:12)
node-pre-gyp ERR! stack     at Function.Module._load (module.js:438:3)
node-pre-gyp ERR! System Darwin 16.7.0
node-pre-gyp ERR! command "/Users/cwilliams/.nvm/versions/node/v6.10.2/bin/node" "/Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/cwilliams/repos/titanium_mobile/node_modules/node-ios-device
node-pre-gyp ERR! node -v v6.10.2
node-pre-gyp ERR! node-pre-gyp -v vhttps://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.6.34.tgz
node-pre-gyp ERR! not ok 
Cannot read property 'version' of null

Specifically, you see: node-pre-gyp ERR! node-pre-gyp -v vhttps://registry.npmjs.org/node-pre-gyp/-/node-pre-gyp-0.6.34.tgz

Looking at the package.json files in my node_modules folder after an npm5 install, I see things like:

{
  "version": "https://registry.npmjs.org/set-blocking/-/set-blocking-2.0.0.tgz"
}

So semver.parse is returning null because these aren't really semantic versioning strings, but urls of resolved packages.
Ultimately I'm not sure if this is a node-pre-gyp "bug" that you'd need to add a workaround for, or it's an npm5 bug. Certainly feels more like an npm bug to me, but then maybe they need/intend for the version value to be a URL for the future.

springmeyer · 2017-06-02T17:31:57Z

Thanks for the report and digging everyone. As the current maintainer of node-pre-gyp my preference here is to:

Recommend people workaround for now by avoiding npm5
Wait for this to be fixed in npm5: npm5 package-lock.json uses resolved URL for version property of existing node_modules npm/npm#16926

floriantraber · 2017-06-03T19:28:07Z

workaround: Remove the lock file.

rm .\package-lock.json

Alexis-Bize · 2017-06-04T00:07:37Z

Worked for me, thanks @floriantraber!

mattbell87 · 2017-06-05T00:54:57Z

@floriantraber Thanks!

dhniels · 2017-06-05T19:38:05Z

If you remove the lock file doesnt it just regenerate it again after running npm install?

borislemke · 2017-06-09T15:07:22Z

in my case the package-lock.json file got included in the project's commit. When cloning the repo on another machine and doing npm i, this error would be thrown. We added the lock file to .gitignore and all works well.

alexjlockwood · 2017-06-09T15:15:29Z

@borislemke That may work as a temporary solution, but the package-lock.json file is meant to be committed to source control.

maifs · 2017-06-10T12:22:22Z

I am facing the same issue .
what do i need to fix it ?
Kindly guide. thank you.

https://stackoverflow.com/questions/44462901/how-to-install-latest-angular-cli-using-visual-studio-2017-node-js-interactive-w

sergioviniciuss · 2017-06-14T00:59:24Z

Same issue in here..

alexjlockwood · 2017-06-14T12:32:05Z

I added package-lock=false to the .npmrc file in my repo's root directory in order to temporarily workaround the issue. Seemed cleaner than adding it to the .gitignore. :P

dustintheweb · 2017-06-18T15:30:56Z

@alexjlockwood worked like a champ

See mapbox/node-pre-gyp#298 for details.

…-work-around-node-pre-gyp-bug do not use `package-lock.json` (workaround for `node-pre-gyp` bug on npm5: mapbox/node-pre-gyp#298) (fixes #439)

lmuzquiz · 2017-09-05T14:51:03Z

I was dealing with this errors many hours until i deleted my package-lock.json file and then ran npm install again. I know the file is re-generated with each npm install but i dont get the node pre gyp errors anymore. So go figure...
Thanks to all of you.

springmeyer · 2017-09-07T20:26:43Z

In addition to removing package-lock.json I've found another workaround.

I was able to replicate this on OS X with:

node v8.4.0
npm 5.3.0

this package.json:

{
  "name": "master",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "sqlite3": "https://github.com/mapbox/node-sqlite3/tarball/d18c1e97de9478aab27067638899b068e6d8ed03"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

And by seeding the node_modules/node-pre-gyp folder with node-pre-gyp@0.6.36.

It seems that something about the install noticing node-pre-gyp already in the node_modules (which is okay and often the case) triggers this odd behavior in npm.

Locally I've been able to solve by doing:

{
  "name": "master",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "sqlite3": "https://github.com/mapbox/node-sqlite3/tarball/master"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

Which includes TryGhost/node-sqlite3@34e1a40. So, my hunch is that npm ls is involved here somehow.

refs https://gist.github.com/springmeyer/96f9b937d2ecf71f8b3dc3c58b92be9b

…1e6411, #298 (comment)

…p#298].

zouhairkhallaf · 2017-10-26T17:28:02Z

Thank you @floriantraber for pointing out the removal of package-lock.json. I did that and was still getting the error, but when I removed my node_modules folder and then ran npm install again, It worked. So remove both package-lock.json and node_module folder and ran npm install and that should work.

skylarmb · 2017-10-30T21:30:27Z

I fixed this by updating to fsevents@1.1.2 which fixes this: fsevents/fsevents#172

…p#298].

, 71e6411, mapbox#298 (comment)

This was referenced Jun 1, 2017

Can't install electron 1.7.1 locally using npm 5 electron-userland/electron-prebuilt#258

Closed

npm5 issues? fsevents/fsevents#172

Closed

zackkrida mentioned this issue Jun 1, 2017

Error on npm install after update to Node 8 vuejs-templates/pwa#30

Closed

sgtcoolguy mentioned this issue Jun 2, 2017

[TIMOB-24591] Use package-lock.json instead of checking in node_modules tidev/titanium-sdk#9048

Merged

sgtcoolguy mentioned this issue Jun 2, 2017

npm5 package-lock.json uses resolved URL for version property of existing node_modules npm/npm#16926

Closed

3 tasks

springmeyer mentioned this issue Jun 2, 2017

Support for node8 TryGhost/node-sqlite3#826

Closed

p120ph37 mentioned this issue Jun 6, 2017

Electron support Robot/robot-js#20

Merged

puppycodes mentioned this issue Jun 16, 2017

Npm5 using a URL value dat-ecosystem-archive/hypercloud#113

Open

viankakrisna mentioned this issue Jun 18, 2017

Create react app dependency error facebook/create-react-app#2558

Closed

jaredhirsch added a commit to mozilla-services/screenshots that referenced this issue Jun 27, 2017

Disallow package-lock for npm5 fsevents compatibility

1b200aa

See mapbox/node-pre-gyp#298 for details.

jaredhirsch added a commit to mozilla-services/screenshots that referenced this issue Jun 27, 2017

Disallow package-lock for npm5 fsevents compatibility

6586a59

See mapbox/node-pre-gyp#298 for details.

jaredhirsch mentioned this issue Jun 27, 2017

Disallow package-lock for npm5 fsevents compatibility mozilla-services/screenshots#3066

Merged

ai mentioned this issue Jul 9, 2017

Errors on install with Node.js 8.1.3 and npm 5.1.0 ai/size-limit#3

Closed

cvan mentioned this issue Jul 11, 2017

do not use package-lock.json (workaround for node-pre-gyp bug on npm5: mapbox/node-pre-gyp#298) (fixes #439) aframevr/aframe-site#440

Merged

7sempra mentioned this issue Jul 21, 2017

Disable npm's package lock for now eve-val/eve-roster#259

Merged

gideonthomas mentioned this issue Jul 28, 2017

Fix broken npm thing mozilla/mozillafestival.org#667

Merged

springmeyer pushed a commit that referenced this issue Sep 7, 2017

fix docs to avoid mentioning the deprecated prepublish - refs #291, 7…

818568b

…1e6411, #298 (comment)

springmeyer mentioned this issue Sep 8, 2017

Successive npm installs resulting in slight differences in lockfile (npm@5) npm/npm#16728

Open

ShubhamGupta pushed a commit to vinsol-spree-contrib/spree-on-react that referenced this issue Oct 16, 2017

Adding package-lock.json to npmrc. Temporary fix: [mapbox/node-pre-gy…

c97271e

…p#298].

matthewharwood mentioned this issue Nov 8, 2017

Universal/Prerendering builds Error: Cannot read property 'version' of null nrwl/nx#96

Closed

jongb mentioned this issue Nov 30, 2017

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

Open

millzpaugh mentioned this issue Mar 29, 2018

mason-js port mapbox/vtquery#67

Closed

believe2world added a commit to believe2world/react-spree-bunny that referenced this issue Apr 28, 2023

Adding package-lock.json to npmrc. Temporary fix: [mapbox/node-pre-gy…

9bc5fbf

…p#298].

hyj1991 pushed a commit to X-Profiler/node-pre-gyp that referenced this issue Jun 16, 2023

fix docs to avoid mentioning the deprecated prepublish - refs mapbox#291

e0dcf73

, 71e6411, mapbox#298 (comment)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

npm@5 TypeError: Cannot read property 'version' of null #298

npm@5 TypeError: Cannot read property 'version' of null #298

yvele commented Jun 1, 2017 •

edited

sgtcoolguy commented Jun 2, 2017 •

edited

springmeyer commented Jun 2, 2017

floriantraber commented Jun 3, 2017

Alexis-Bize commented Jun 4, 2017

mattbell87 commented Jun 5, 2017

dhniels commented Jun 5, 2017

borislemke commented Jun 9, 2017

alexjlockwood commented Jun 9, 2017

maifs commented Jun 10, 2017

sergioviniciuss commented Jun 14, 2017

alexjlockwood commented Jun 14, 2017

dustintheweb commented Jun 18, 2017

lmuzquiz commented Sep 5, 2017

springmeyer commented Sep 7, 2017 •

edited

zouhairkhallaf commented Oct 26, 2017

skylarmb commented Oct 30, 2017 •

edited

npm@5 TypeError: Cannot read property 'version' of null #298

npm@5 TypeError: Cannot read property 'version' of null #298

Comments

yvele commented Jun 1, 2017 • edited

sgtcoolguy commented Jun 2, 2017 • edited

springmeyer commented Jun 2, 2017

floriantraber commented Jun 3, 2017

Alexis-Bize commented Jun 4, 2017

mattbell87 commented Jun 5, 2017

dhniels commented Jun 5, 2017

borislemke commented Jun 9, 2017

alexjlockwood commented Jun 9, 2017

maifs commented Jun 10, 2017

sergioviniciuss commented Jun 14, 2017

alexjlockwood commented Jun 14, 2017

dustintheweb commented Jun 18, 2017

lmuzquiz commented Sep 5, 2017

springmeyer commented Sep 7, 2017 • edited

zouhairkhallaf commented Oct 26, 2017

skylarmb commented Oct 30, 2017 • edited

yvele commented Jun 1, 2017 •

edited

sgtcoolguy commented Jun 2, 2017 •

edited

springmeyer commented Sep 7, 2017 •

edited

skylarmb commented Oct 30, 2017 •

edited