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

NPM package metadata left behind in a confusing way when a user intends to delete the entire package

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.13.0, 3.37.3
    • Fix Version/s: None
    • Component/s: Browse Storage, NPM
    • Labels:

      Description

      Use Case

      A user wishes to manually delete an npm package from a repo, including its metadata, and all the related tgz files that may be present, with a single operation.

      Problem

      The current behaviour is confusing, can lead to a broken browse view and a false sense that the entire package was deleted:

      To accomplish this using browse view.
      1. Navigate to the npm package root and click on it.
      2. In right panel, click Delete Folder
      3. Acknowledge prompt.
      4. Refresh the Browse view.
      5. Select package root for the same component again
      6. Click Delete asset
      7. Now the tgz and package metadata are gone from that repo

      Video:

      Alternative that some users try:

      1. Navigate to the npm package root and click on it.
      2. In right panel, click Delete Asset
      3. Confirm deletion.
      4. Browse view does not refresh.
      5. Refresh browse view manually. Receive UI error "Unable to show requested tree" because the URL is still http://localhost:8081/#browse/browse:npm-proxy:colors
      6. There is no way to browse to the tgz assets left behind.

      Keep going...

      7. Use Search to find the dangling npm assets. Select each dangling npm tgz file associated with that package. ( you can't easily tell which repo they are in so you have to select each one manually.
      8. Search for the package by name - the results show by tgz asset ( many per one ).
      9. Select a dangling npm tgz search result is selected, click Delete Component to delete the package tgz files

      Expected

      The browse view should provide a single operation to accomplish a complete deletion of an npm package.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Joe Tom Joe Tom
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title