Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

20
  • Is there any more meaningful output when you do npm --loglevel=silly install? Commented Jan 7, 2017 at 18:27
  • 13
    @hardillb - not really a problem with my internet or machine speed. Can download a full install of linux faster than npm install takes to grab a few scripts -- on the same computer. Comparitively, can run haversine on a non-index recordset in mysql over 1 million records faster. Commented Jan 7, 2017 at 18:30
  • 1
    "I suspect there is something wrong with my packages.json or the command I am running npm install" - I don't think so. I installed modules here in less than 1 min with your package.json with npm v3.5.2 and node v4.2.6. I suggest you update node and npm. Commented Jan 7, 2017 at 19:09
  • 10
    That is a very, very old version of npm. I wouldn't be surprised if this is a bug in npm that was fixed in a later version. Can you update your npm to latest? sudo npm install -g npm@latest Commented Jan 7, 2017 at 19:11
  • 1
    Generally speaking, don't rely on package managers like apt to maintain up-to-date software. I would strongly recommend purging the node/npm combo you installed from apt and following the instructions on nodejs.org to install the latest release. Commented Jan 7, 2017 at 19:54