Member Avatar for SimonIoa

Hello i am getting an error on log about npm... Any suggestion?

PATH=.\node_modules.bin;C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Web\External;%PATH%;C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\cmd;C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Git\mingw32\bin
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Web\External\npm.CMD" install
npm WARN deprecated babili@0.0.10: babili has been renamed to babel-minify. Please update to babel-minify
npm WARN engine webpack@2.2.1: wanted: {"node":">=4.3.0 <5.0.0 || >=5.10"} (current: {"node":"5.4.1","npm":"3.3.4"})
npm WARN deprecated babel-preset-babili@0.0.10: babili has been renamed to babel-minify. Please update to babel-preset-minify
npm WARN install Couldn't install optional dependency: Unsupported
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Web\External\Node.exe" "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Web\External\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v5.4.1
npm ERR! npm v3.3.4
npm ERR! code ENOENT
npm ERR! errno ENOENT
npm ERR! syscall getaddrinfo
npm ERR! enoent getaddrinfo ENOENT registry.npmjs.org:443
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Simon\Cookies\Desktop\Various Scripts\ionic\npm-debug.log

  • 2 Contributors
  • 2 Replies
  • 873 Views
  • 16 Hours Discussion Span
  • Latest Post Latest Post by SimonIoa

Dani AI

Generated

A few concise troubleshooting notes and practical checks that explain the error and cover the fixes people commonly use (condensed from the longer threads pointed to). noted the error disappeared; below are the quick, reliable steps that usually resolve it.

First, this is a network/name‑resolution problem: the npm client could not reach the registry host. Verify the registry is reachable from your machine (open https://registry.npmjs.org/ in a browser) and that simple name/DNS resolution works. If the registry is unreachable from the CLI but loads in your browser, suspect a proxy or per‑process/network rule. (stackoverflow.com)

Check npm/OS proxy and registry settings next. Use:

npm config get registry
npm config get proxy
npm config get https-proxy

Remove incorrect proxy entries or set correct ones (or remove them if you are not behind a proxy):

npm config rm proxy
npm config rm https-proxy
npm config set registry https://registry.npmjs.org/

Also check/clear environment vars like HTTP_PROXY and HTTPS_PROXY if present. The npm config docs cover these options and how npm honors system proxies. (docs.npmjs.com)

If configs look fine, run npm diagnostics and refresh the cache:

npm doctor
npm cache clean --force
(remove node_modules and package-lock.json, then) npm install

npm doctor will report obvious misconfigurations and whether the CLI can reach the registry; clearing/verifying the cache removes corrupted state that sometimes aborts installs. (docs.npmjs.com)

Other common traps: corporate firewalls or local antivirus can block command‑line tools (some users fixed it by adjusting firewall rules), proxy credentials with special characters need URL‑encoding, and Visual Studio may ship or prefer a bundled Node/npm—make sure the IDE and your shell use the intended Node install or adjust External Web Tools/PATH. If problems persist, include the npm debug log when asking for help. (stackoverflow.com)

Recommended Answers

All 2 Replies

Member Avatar for SimonIoa

OK Fixed it!!!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.