npm / npm/rfcs

[RRFC] bare `npm unlink` should work

Open
#576 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
777
Forks
267
PR merge metrics
No merged PRs in 30d

Description

Motivation ("The Why")

npm link works.

npm unlink doesn't.

Example
$ npm unlink
npm ERR! Must provide a package name to remove

npm ERR! A complete log of this run can be found in:
npm ERR!     $HOME/.npm/_logs/2022-04-21T16_17_37_636Z-debug-0.log

Seems pretty straightforward to me - if i can npm foo i should be able to npm unfoo.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the motivation and shell example in this RFC issue, then investigate how npm link and npm unlink currently differ. A complete proposal should define the expected behavior for bare npm unlink and provide enough detail for the npm CLI implementation to be evaluated.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.