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

Install npm issues #13450

Closed
ahkmunna opened this issue Jul 21, 2016 · 3 comments
Closed

Install npm issues #13450

ahkmunna opened this issue Jul 21, 2016 · 3 comments

Comments

@ahkmunna
Copy link

ahkmunna commented Jul 21, 2016

I have issues with npm install:
Here is my npm-debug.log :

npm install
npm WARN deprecated grunt-contrib-livereload@0.1.1: Deprecated in favor of grunt-contrib-watch which now have Livereload support built-in.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
loadDep:qs → addNamed     ▄ ╢████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
loadDep:sntp → 304        ▌ ╢████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░╟
WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"5.1.0","npm":"3.4.1"})
WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"5.1.0","npm":"3.4.1"})
WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"5.1.0","npm":"3.4.1"})
npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm ERR! Darwin 15.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v5.1.0
npm ERR! npm  v3.4.1

npm ERR! No compatible version found: phantomjs@~1.8.1
npm ERR! Valid install targets:
npm ERR! 2.1.7, 2.1.3, 2.1.3-deprecated, 2.1.2, 2.1.1, 1.9.20, 1.9.19, 1.9.18, 1.9.17, 1.9.16, 1.9.15, 1.9.13, 1.9.12, 1.9.11, 1.9.10, 1.9.9, 1.9.8, 1.9.7-15, 1.9.7-14, 1.9.7-13, 1.9.7-12, 1.9.7-11, 1.9.7-10, 1.9.7-9, 1.9.7-8, 1.9.7-7, 1.9.7-6, 1.9.7-5, 1.9.7-4, 1.9.7-3, 1.9.7-1, 1.9.6-0, 1.9.2-6, 1.9.2-5, 1.9.2-4, 1.9.2-3, 1.9.2-2, 1.9.2-1, 1.9.2-0, 1.9.1-9, 1.9.1-8, 1.9.1-7, 1.9.1-6, 1.9.1-5, 1.9.1-4, 1.9.1-3, 1.9.1-2, 1.9.1-0, 1.9.0-6, 1.9.0-5, 1.9.0-4, 1.9.0-3, 1.9.0-2, 1.9.0-1, 1.9.0-0, 1.8.2-3, 1.8.2-2, 1.8.2-1, 1.8.2-0, 1.8.1-3, 1.8.1-2, 1.8.1-1, 1.8.0-1, 0.2.6, 0.2.5, 0.2.4, 0.2.3, 0.2.2, 0.2.1, 0.2.0, 0.1.1, 0.1.0, 0.0.9, 0.0.8, 0.0.7, 0.0.6, 0.0.5, 0.0.4, 0.0.3, 0.0.2, 0.0.1
npm ERR!
npm ERR!

npm-debug.txt

@kenany
Copy link
Contributor

kenany commented Jul 21, 2016

@ahkmunna Can I see your package.json's "dependencies" and "devDependencies"?

@ahkmunna
Copy link
Author

Here is my package.json file:

{
  "name": "Strut",
  "version": "0.4.0",
  "devDependencies": {
    "grunt": "~1.0.1",
    "grunt-contrib-handlebars": "~0.5.10",
    "grunt-contrib-copy": "~0.4.0",
    "grunt-contrib-concat": "~0.3.0",
    "grunt-contrib-uglify": "~0.2.0",
    "grunt-contrib-jshint": "~0.6.0",
    "grunt-contrib-cssmin": "~0.6.0",
    "grunt-contrib-connect": "0.3.0",
    "grunt-contrib-clean": "~0.4.1",
    "grunt-contrib-htmlmin": "~0.1.3",
    "grunt-contrib-imagemin": "~0.1.4",
    "grunt-contrib-watch": "~0.4.0",
    "grunt-contrib-livereload": "0.1.1",
    "grunt-usemin": "~0.1.9",
    "grunt-contrib-requirejs": "~0.4.1",
    "grunt-mocha": "~0.2.2",
    "grunt-open": "~0.2.0",
    "matchdep": "~0.1.2",
    "grunt-text-replace": "~0.3.2"
  },
  "engines": {
    "node": ">=0.8.0"
  }
}

@npm-robot
Copy link

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

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

No branches or pull requests

4 participants