Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-19384

NPM Group fails to forward requests for updating to members

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.15.0, 3.15.1, 3.15.2, 3.16.0
    • Fix Version/s: 3.16.0
    • Component/s: NPM
    • Story Points:
      3

      Description

      When proxying NPM packages, the metadata max-age does not work, resulting in new versions of a package not to be downloaded.

      To reproduce:

      1. Create an NPM proxy repo, proxying to a hosted NPM repo on another NXRM 3 instance (this can be any NPM registry, a remote Nexus 3 is only for the sake of convenience).
      2. Create an NPM group repo and the add the NPM proxy repo to it.

      3. Upload v1.0.0 of NPM package to the remote hosted NPM repo.
      4. run npm i <package>@1.0.0 against group repo - install works (expected).
      5. run npm i <package>@2.0.0 against group repo - install fails (expected).

      6. Upload v2.0.0 of NPM package to the remote hosted NPM repo.

      7. Invalidate the proxy repo cache or wait for 'metadata max-age' time to pass.
      8 run npm i <package>@2.0.0 against group repo - install fails (unexpected).

      9. Invalidate the group repo cache.
      10. run npm i <package>@2.0.0 against group repo - this time install works.

        Attachments

          Activity

            People

            Assignee:
            jbryan Jeremy Bryan
            Reporter:
            hardeepn Hardeep Nagra
            CC:
            João França
            Last Updated By:
            Mark Chester Mark Chester
            Team:
            NXRM - Cypher
            Votes:
            5 Vote for this issue
            Watchers:
            29 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title