Skip to content

i am getting below error when i do npm install. does anyone know any solution? #1240

Closed

Description

@MansiRungta

npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ETIMEDOUT: request to https://registry.npmjs.org/@types%2fnode failed, reason: connect ETIMEDOUT 104.16.16.35:443
npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
[ .................] / fetchMetadata: sill pacote version manifest for event-stream@3.3.4 fetched in 133086ms

Activity

  1. w3dg commented on May 12, 2020

    @w3dg

    are you connected to the internet while doing npm install?

  2. sdancer75 commented on Oct 6, 2020

    @sdancer75

    Hi,

    Today I met the same problem.

    Running the following docker script

    RUN npm install or npm uninstall npm -g

    I got the following errors.

    Step 15/19 : RUN npm install
     ---> Running in 0a0af5823fd9
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: acorn@2.7.0 (node_modules/acorn):
    npm WARN network SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/acorn/-/acorn-2.7.0.tgz failed, reason: connect ETIMEDOUT 173.245.59.72:443
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: acorn-globals@1.0.9 (node_modules/acorn-globals):
    npm WARN network SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/acorn-globals/-/acorn-globals-1.0.9.tgz failed, reason: connect ETIMEDOUT 173.245.59.72:443
    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: abab@1.0.4 (node_modules/abab):
    npm WARN network SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/abab/-/abab-1.0.4.tgz failed, reason: connect ETIMEDOUT 173.245.59.72:443
    
    
    npm ERR! code ETIMEDOUT
    npm ERR! errno ETIMEDOUT
    npm ERR! network request to https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz failed, reason: connect ETIMEDOUT 173.245.59.72:443
    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'
    

    here are my registry and proxy settings.

    sdancer@AsusROG:/mnt/d/git_projects/dynamic_forms/forms2/docker$ npm config get registry
    https://registry.npmjs.org/
    sdancer@AsusROG:/mnt/d/git_projects/dynamic_forms/forms2/docker$ npm config get http-proxy
    undefined
    sdancer@AsusROG:/mnt/d/git_projects/dynamic_forms/forms2/docker$ npm config get https-proxy
    null
    sdancer@AsusROG:/mnt/d/git_projects/dynamic_forms/forms2/docker$ npm config list
    ; cli configs
    metrics-registry = "https://registry.npmjs.org/"
    scope = ""
    user-agent = "npm/6.14.4 node/v10.19.0 linux x64"
    
    ; builtin config undefined
    globalconfig = "/etc/npmrc"
    globalignorefile = "/etc/npmignore"
    prefix = "/usr/local"
    
    ; node bin location = /usr/bin/node
    ; cwd = /mnt/d/git_projects/dynamic_forms/forms2/docker
    ; HOME = /home/sdancer
    ; "npm config ls -l" to show all defaults.
    

    I added to my script the following commands but nothing changed.

    # Install packages
    RUN npm config delete http-proxy
    RUN npm config delete https-proxy
    
    RUN npm config rm proxy
    RUN npm config rm https-proxy
    
    RUN set HTTP_PROXY=null
    RUN set HTTPS_PROXY=null
    RUN npm cache verify
    RUN npm install
    

    @debopamgupta Yes I am connected to the internet while doing npm install that maybe the is also an older version already installed.

  3. darcyclarke commented on Jun 2, 2021

    @darcyclarke
    Contributor

    npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

    If your bug is preproducible on v7, please re-file this issue using our new issue template.

    If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

    Closing: This is an automated message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Release 6.xwork is associated with a specific npm 6 release

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions