logrocket-fuzzy-search-sanitizer icon indicating copy to clipboard operation
logrocket-fuzzy-search-sanitizer copied to clipboard

Published 20 hours ago • verified publisher icon LogRocket

Use default npm registry instead of custom registry in package-lock.json

Open satyadeepk opened this issue 3 years ago • 1 comments

Previously the package-lock.json file uses a custom npm registry for most of the packages. nexus.int.ally.com

It was causing build failures when directly pointing to the Github repo on CI as that custom registry is not live anymore.

  519 error npm ERR! network request to https://nexus.int.ally.com/nexus/repository/npm-group/wrappy/-/wrappy-1.0.2.tgz failed, reason: getaddrinfo ENOTFOUND nexus.int.ally.com

So fixed it to use the default npm registry registry.npmjs.org

satyadeepk avatar Feb 03 '21 18:02 satyadeepk