You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm WARN deprecated [email protected]: this package is now deprecated
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to http://blip.strongloop.com/[email protected] failed, reason: getaddrinfo ENOTFOUND blip.strongloop.com blip.strongloop.com:80
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-03-14T07_48_24_599Z-debug.log
The command '/bin/sh -c npm install' returned a non-zero code: 1
Related Issues
The text was updated successfully, but these errors were encountered:
Steps to reproduce
npm install on existing project
Current Behavior
npm ERR! network request to http://blip.strongloop.com/[email protected] failed, reason: getaddrinfo ENOTFOUND
Expected Behavior
npm install to be successfull
Link to reproduction sandbox
Additional information
Related Issues
The text was updated successfully, but these errors were encountered: