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

After NPM warehouses aggregate multiple hosted warehouses, the tag of NPM is not normal

Details

    • Bug
    • Resolution: Unresolved
    • Blocker
    • None
    • 3.29.0
    • NPM

    Description

      I create three rep:npm-nr-group(group)、npm-nr-001(hosted)、npm-nr-002(hosted)

      npm-nr-group

      ----npm-nr-001
      ----npm-nr-002

       

      I publish different versions of NPM packages in two hosted repositories:

      1. version 1.0.16

      npm --registry=http://xxxx/nexus/repository/npm-nr-001 publish --tag develop

       

      1. version 1.0.17

      npm --registry=http://xxxx/nexus/repository/npm-nr-002 publish --tag develop

       

      When I successfully pushed, I checked the version from the group warehouse and found that:

      npm --registry=http://xxxx/nexus/repository/npm-nr-group  dist-tag ls demo004

      develop: 1.0.17

       

      npm --registry=http://xxxx/nexus/repository/npm-nr-group  view demo004@develop

      demo004@1.0.16 | Proprietary | deps: none | versions: 9

      ...
      dist-tags:
      develop: 1.0.16

       

      npm --registry=http://xxxx/nexus/repository/npm-nr-group  i demo004@develop

      + demo004@1.0.16
      updated 1 package in 0.316s

       

      The result obtained by "npm dist-tag ls xxxx" is correct, but "npm view xxx" and "npm install xxxx" are wrong

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            hanxinhang hanxinhang
            Joe Tom Joe Tom
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              tigCommentSecurity.panel-title