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

getaddrinfo ENOENT registry.npmjs.org:443 Error By npm itself #21173

Open
2 tasks
ghost opened this issue Jul 9, 2018 · 2 comments
Open
2 tasks

getaddrinfo ENOENT registry.npmjs.org:443 Error By npm itself #21173

ghost opened this issue Jul 9, 2018 · 2 comments

Comments

@ghost
Copy link

ghost commented Jul 9, 2018

I'm opening this issue because:

  • npm is crashing.
  • Other (see below for feature requests):
    npm itself error

What's going wrong?

When i tried to create a new project. I am hitting an error as npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ENOENT: request to https://registry.npmjs.org/typescript failed, reason: getaddrinfo ENOENT registry.npmjs.org:443
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
npm WARN deprecated istanbul-lib-hook@1.2.1: 1.2.0 should have been a major version bump
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Digital Adarsh\AppData\Roaming\npm-cache_logs\2018-07-09T14_18_12_430Z-debug.log

@DanielRuf
Copy link

Please check your network conditions and DNS. This should work https://registry.npmjs.org/typescript

@DanielRuf
Copy link

Also try multiple npm i until it works.

You may have to delete the lockfile and node_modules and in some cases npm cache clean --force also helps.

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

2 participants