dep
dep copied to clipboard
dep hung for a minute until I interrupted
Summary
on the second last run, dep hung for a minute until I interrupted it, but the other two runs it installed in a dozen or so seconds. https://github.com/watilde/dep/issues/7
Steps to reproduce behavior
$ dep i; ls -l node_modules/eslint/bin/eslint.js
Resolving dependencies
Installing dependencies
^C
Expected behavior
It shouldn't be hung.
Actual behavior
It's hung for a minute.
On https://github.com/strongloop/strong-deploy
sn/strong-deploy (master u=) % dep i
Resolving dependencies
Installing dependencies
Installed 808 packages in 46.812s
This says it took 46 seconds, but I think it took much longer, I'd been waiting, then went to have a conversation, and it was done when I came back. So, I tried again, because I think the timing info might be wrong.
sn/strong-deploy (master u=) % git clean -x -d
Removing node_modules/
sn/strong-deploy (master u=) % time dep i
Resolving dependencies
^C
dep i 5.76s user 0.70s system 1% cpu 6:32.58 total
Over 6 minutes, but no install.
This is on 16.04 ubuntu, x64, fwiw.
I'm running again, to see if its deterministic.
sn/strong-deploy (master u=) % time dep i
Resolving dependencies
^C
dep i 6.38s user 0.69s system 1% cpu 5:56.61 total
Seems to happen each time.
Oops, I actually could install the deps in 20s.
click here
$ git clone https://github.com/strongloop/strong-deploy.git
$ cd strong-deploy
$ dep i
Resolving dependencies
Installing dependencies
Installed 901 packages in 20.094s
With npm without cache, it took almost same time:
click here
$ npm cache clean -f
npm WARN using --force I sure hope you know what you are doing.
$ npm i
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: connect 2.x series is deprecated
added 544 packages in 23.391s
I will try again to figure out the problem anyway.
If you have suggestions on diagnostics I can run, I would happily do it.