[BUG] 404 on unpublish does not show up on cli
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Current Behavior:
When unpublish fails the cli does not output any errors or indicate that the unpublish was not successful
Expected Behavior:
Some sort of output is returned letting the user know that the unpublish was not successful
Steps To Reproduce:
Run npm unpublish on either a nonexistent package, one you do not have access to, or while logged out of the cli.
Environment:
- OS: macOS Catalina
- Node: 12.20.1
- npm: 7.4.0
This has been mentioned in previous issues. This issue is meant to consolidate them into a specific issue dealing with the output, versus the various other tangential issues (i.e. not being logged in).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with npm unpublish against a nonexistent or unauthorized package, or while logged out. Trace the unpublish command's handling of the 404 response and identify where command output is suppressed. Done means each listed failure produces a clear error indicating that unpublish was unsuccessful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100