npm install --dev infinite install (windows 7 ?) #3043

Closed
happyspace opened this Issue Jan 10, 2013 · 5 comments

Projects

None yet

4 participants

@happyspace

Restify npm install --dev runs forever with a bunch of errors when non empty directories are attempted to be deleted. Wish I could put the log files on the issue since they are fairly big. See below for some of the errors. This is easy for me to reproduce and has a work around. I am pretty sure this is a windows issue since I assume the the developers of Restify must run --dev installs.

Platform: Windows 7 (yes git is installed and runs from command line)

Steps to reproduce

  1. clone Restify
  2. within Restify run 'npm install --dev'

Work around

  1. run npm install
  2. install dev modules individually

Did an search on --dev and did not find an issue but did find the same behavior in this issue turned up in a Google search #2277.

Some errors:

C:\git\node-restify>npm install --dev
npm http GET https://registry.npmjs.org/nodeunit/0.7.4
npm http GET https://registry.npmjs.org/keep-alive-agent/0.0.1
npm http GET https://registry.npmjs.org/lru-cache/2.2.1
npm http GET https://registry.npmjs.org/http-signature/0.9.9
npm http GET https://registry.npmjs.org/once/1.1.1
npm http GET https://registry.npmjs.org/qs/0.5.3
npm http GET https://registry.npmjs.org/semver/1.1.2
npm http GET https://registry.npmjs.org/formidable/1.0.11
npm http GET https://registry.npmjs.org/backoff/1.2.0
npm http GET https://registry.npmjs.org/bunyan/0.17.0

.... errors start

npm http GET https://registry.npmjs.org/burrito
npm ERR! Error: ENOENT, chmod 'C:\git\node-restify\node_modules\semver\node_modules\tap\node_modules\difflet\node_module
s\traverse\test\json.js'
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js"
"install" "--dev"
npm ERR! cwd C:\git\node-restify
npm ERR! node -v v0.8.14
npm ERR! npm -v 1.1.70
npm ERR! path C:\git\node-restify\node_modules\semver\node_modules\tap\node_modules\difflet\node_modules\traverse\test\j
son.js
npm ERR! fstream_path C:\git\node-restify\node_modules\semver\node_modules\tap\node_modules\difflet\node_modules\travers
e\test\json.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chmod
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack Writer._finish (C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:305:1
9)
npm ERR! fstream_stack Object.oncomplete (fs.js:297:15)
npm ERR! Error: ENOENT, lstat 'C:\git\node-restify\node_modules\semver\node_modules\tap\node_modules\difflet\node_module
s\tap\test\timeout.js'
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:

.... later in the log

npm http 304 https://registry.npmjs.org/difflet
npm http 304 https://registry.npmjs.org/deep-equal
npm ERR! Error: ENOENT, lstat 'C:\git\node-restify\node_modules\http-signature\node_modules\tap\node_modules\difflet\nod
e_modules\ent\node_modules\tape\node_modules\falafel\node_modules\esprima\doc\index.html'
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js"
"install" "--dev"
npm ERR! cwd C:\git\node-restify
npm ERR! node -v v0.8.14
npm ERR! npm -v 1.1.70
npm ERR! path C:\git\node-restify\node_modules\http-signature\node_modules\tap\node_modules\difflet\node_modules\ent\nod
e_modules\tape\node_modules\falafel\node_modules\esprima\doc\index.html
npm ERR! fstream_path C:\git\node-restify\node_modules\http-signature\node_modules\tap\node_modules\difflet\node_modules
\ent\node_modules\tape\node_modules\falafel\node_modules\esprima\doc\index.html
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\Program Files\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:297:15)
npm http GET https://registry.npmjs.org/mime/1.2.6
npm http GET https://registry.npmjs.org/range-parser/0.0.4
npm http GET https://registry.npmjs.org/supertest/0.0.1

@bobrik
Contributor
bobrik commented May 12, 2013

Same for OS X, npm 1.2.18, node v0.10.5

npm install --dev zk-redis-queue

Installation never ends, showing up in output from time to time:

npm ERR! Error: ENOENT, lstat '/Users/bobrik/temp/node_modules/zk-redis-queue/node_modules/nop/node_modules/mocha/node_modules/coffee-script/node_modules/jison/node_modules/browserify/node_modules/umd/node_modules/rfile/node_modules/mocha/node_modules/growl/package.json'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Darwin 12.3.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "--dev" "zk-redis-queue"
npm ERR! cwd /Users/bobrik/temp
npm ERR! node -v v0.10.5
npm ERR! npm -v 1.2.18
npm ERR! path /Users/bobrik/temp/node_modules/zk-redis-queue/node_modules/nop/node_modules/mocha/node_modules/coffee-script/node_modules/jison/node_modules/browserify/node_modules/umd/node_modules/rfile/node_modules/mocha/node_modules/growl/package.json
npm ERR! fstream_path /Users/bobrik/temp/node_modules/zk-redis-queue/node_modules/nop/node_modules/mocha/node_modules/coffee-script/node_modules/jison/node_modules/browserify/node_modules/umd/node_modules/rfile/node_modules/mocha/node_modules/growl/package.json
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
@adambaker adambaker referenced this issue in robotlolita/claire Jun 11, 2013
Closed

npm install fails without livescript #26

@luk-
Contributor
luk- commented Jul 24, 2013

@happyspace if you're running npm install in a package directory, you do not need to specify --dev.

@luk- luk- closed this Jul 24, 2013
@bobrik
Contributor
bobrik commented Jul 24, 2013

@luk-, I run:

mkdir /tmp/ttt
cd /tmp/ttt
npm install --dev zk-redis-queue

and it never ends.

@domenic
Member
domenic commented Jul 24, 2013

Remove the --dev and it will work.

@bobrik
Contributor
bobrik commented Jul 24, 2013

@domenic, okay. I don't see --dev option in npm help install anymore, but it is still broken.

@acmacalister acmacalister referenced this issue in loopj/capistrano-node-deploy Aug 16, 2013
Merged

removed npm --dev and --production flags #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment