When a user deletes an npm package tarball from a repository, NXRM first checks for its version reference in the package's root level metadata. This is done so the version can be removed from the metadata.
If the version is not found in the package level metadata, then the code which would delete the tarball is skipped. Essentially the code silently fails to do the delete the tarball as requested and nothing is logged explaining what happened.
There must be a normal way to delete a tarball, even if the package root metadata does not reference it, so:
- If a delete operation is aborted for any reason we should clearly log the reason ( applies for any situation, not just this one )
- If the version to be deleted is not in the package level metadata we should log this, but then proceed to delete the requested tarball anyways.