Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

Error during web-starter-kit using 'npm install' #9407

Closed
matt-matt1 opened this issue Aug 25, 2015 · 2 comments
Closed

Error during web-starter-kit using 'npm install' #9407

matt-matt1 opened this issue Aug 25, 2015 · 2 comments
Assignees
Labels

Comments

@matt-matt1
Copy link

As per the instructions on Google Developers, I installed the latest node.js (downloaded, extracted, configured, and built from source on my CentOs 7 machine). Then I downloaded the Web Starter Kit project zip and extracted. Then it said type 'npm install', here's the output:

# npm install
-----
> gifsicle@3.0.1 postinstall /install/web-starter-kit-0.5.4/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle
> node lib/install.js

/
  ✔ gifsicle pre-build test passed successfully

> optipng-bin@3.0.2 postinstall /install/web-starter-kit-0.5.4/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin
> node lib/install.js

  ✔ optipng pre-build test passed successfully

> jpegtran-bin@3.0.4 postinstall /install/web-starter-kit-0.5.4/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-jpegtran/node_modules/jpegtran-bin
> node lib/install.js

  ✔ jpegtran pre-build test passed successfully

> phantomjs@1.9.18 install /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs
> node install.js

Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-linux-x86_64.tar.bz2
Saving to /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2
Receiving...
| [==============================----------] 76% 0.0s-
Received 12854K total.
Extracting tar contents (via spawned process)
Removing /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs/lib/phantom
Copying extracted folder /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2-extract-1440535765143/phantomjs-1.9.8-linux-x86_64 -> /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs/lib/phantom
Writing location.js file
Done. Phantomjs binary available at /install/web-starter-kit-0.5.4/node_modules/gulp-uncss/node_modules/uncss/node_modules/phridge/node_modules/phantomjs/lib/phantom/bin/phantomjs
\
> node-sass@2.1.1 install /install/web-starter-kit-0.5.4/node_modules/gulp-sass/node_modules/node-sass
> node scripts/install.js


> node-sass@2.1.1 postinstall /install/web-starter-kit-0.5.4/node_modules/gulp-sass/node_modules/node-sass
> node scripts/build.js

`linux-x64-node-0.12` exists; testing
Binary is fine; exiting
npm ERR! Linux 3.10.0-229.11.1.el7.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3

npm ERR! shasum check failed for /tmp/npm-8990-96d86018/registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.4.tgz
npm ERR! Expected: f9ce19bf1909608ceb15d97721e23bfdd1e7cf65
npm ERR! Actual:   e73db95a4d3a3ea6216a02c16cec3a85a9fc62c3
npm ERR! From:     https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-2.2.4.tgz
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /install/web-starter-kit-0.5.4/npm-debug.log

/install/web-starter-kit-0.5.4/npm-debug.log ends:

222672 verbose exit [ 1, true ]
222673 verbose unbuild node_modules/browser-sync/node_modules/socket.io
222674 info preuninstall socket.io@1.3.6
222675 info uninstall socket.io@1.3.6
222676 verbose unbuild rmStuff socket.io@1.3.6 from /install/web-starter-kit-0.5.4/node_modules
222677 verbose unbuild rmStuff in /install/web-starter-kit-0.5.4/node_modules/browser-sync/node_modules
222678 info postuninstall socket.io@1.3.6
222679 silly gentlyRm /install/web-starter-kit-0.5.4/node_modules/browser-sync/node_modules/socket.io is being purged from base /install/web-starter-kit-0.5.4
222680 verbose gentlyRm don't care about contents; nuking /install/web-starter-kit-0.5.4/node_modules/browser-sync/node_modules/socket.io
222681 silly vacuum-fs purging /install/web-starter-kit-0.5.4/node_modules/browser-sync/node_modules/socket.io
222682 silly vacuum-fs quitting because other entries in /install/web-starter-kit-0.5.4/node_modules/browser-sync/node_modules
222683 verbose unbuild node_modules/browser-sync
222684 info preuninstall browser-sync@1.9.2
222685 info uninstall browser-sync@1.9.2
222686 verbose unbuild rmStuff browser-sync@1.9.2 from /install/web-starter-kit-0.5.4/node_modules
222687 silly gentlyRm /install/web-starter-kit-0.5.4/node_modules/.bin/browser-sync is being gently removed
222688 silly gentlyRm verifying /install/web-starter-kit-0.5.4 is an npm working directory
222689 silly gentlyRm containing path /install/web-starter-kit-0.5.4 is under npm's control, in /install/web-starter-kit-0.5.4
222690 silly gentlyRm deletion target /install/web-starter-kit-0.5.4/node_modules/.bin/browser-sync is under /install/web-starter-kit-0.5.4
222691 verbose gentlyRm vacuuming from /install/web-starter-kit-0.5.4/node_modules/.bin/browser-sync up to /install/web-starter-kit-0.5.4
222692 info postuninstall browser-sync@1.9.2
222693 silly gentlyRm /install/web-starter-kit-0.5.4/node_modules/browser-sync is being purged from base /install/web-starter-kit-0.5.4
222694 verbose gentlyRm don't care about contents; nuking /install/web-starter-kit-0.5.4/node_modules/browser-sync
222695 silly vacuum-fs purging /install/web-starter-kit-0.5.4/node_modules/browser-sync
222696 silly vacuum-fs quitting because other entries in /install/web-starter-kit-0.5.4/node_modules

What is the problem and how can I fix it?

@kenany
Copy link
Contributor

kenany commented Aug 25, 2015

@matt-matt1 Have you tried npm cache clear?

@ehsalazar ehsalazar self-assigned this Sep 24, 2015
@ehsalazar
Copy link

We haven’t heard back and we’re trying to clean up some issues. If this is still a problem, can you please reply and let us know? We’ll be happy to reopen if necessary.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants