Skip to content
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.

Distinguish between pacote-bugs, user errors, and server issues #24

Open
zkat opened this issue Feb 14, 2017 · 0 comments
Open

Distinguish between pacote-bugs, user errors, and server issues #24

zkat opened this issue Feb 14, 2017 · 0 comments
Labels
enhancement help wanted
Milestone
next

Comments

@zkat
Copy link
Owner

zkat commented Feb 14, 2017

Right now, there's a bunch of errors that get spit out by various deps and such that we use.

The CLI eventually has to make its own decisions about these, but it would be super handy to distinguish between three main error categories:

  • Things the user did wrong (and can fix): auth errors, bad arg or opt syntax, 404s, etc.
  • Things pacote code fucked up with: basically any unexpected conditions
  • Abnormal conditions: bad data, missing content, network timeouts, filesystem failures

This might be a really great first step towards having much richer error reporting data for CLI users to consume -- specially user-level conditions that we might be able to be very specific about.
@zkat zkat added this to the 1.0.0 milestone Feb 14, 2017
strugee pushed a commit to strugee/pacote that referenced this issue Mar 9, 2021
@isaacs
Extract: rimraf dir contents, not dir itself
698e996 
That is, without rm -rf'ing all the child nodes underneath it in the
tree.  This supports overwriting a package in the tree with a new
extraction, _without_ deleting all of the package's child nodes in the
node_module heirarchy.

This allows a better tree reification mechanism that does not trigger
EPERM and other folder removal/modification errors, especially on
Windows.

Fix zkat#24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
next
Development

No branches or pull requests
1 participant
@zkat