Skip to content

Gracefully handle initial npm errors #1505

Closed

Description

@gaearon

Currently, when npm fails for the first time, you end up with an empty project that doesn't work.

We should delete the broken files we added (or the whole folder if we created it), and print a message explaining the problem is with npm, as well as the underlying message.

Activity

  1. added this to the milestone on Feb 9, 2017
  2. chitchu commented on Feb 9, 2017

    @chitchu
    Contributor

    Hi @gaearon

    I would like to work on this. Any tips on which files I should be looking at?

  3. Timer commented on Feb 9, 2017

    @Timer
    Contributor
  4. modified the milestones: 0.9.1, on Feb 11, 2017
  5. added a commit that references this issue on Feb 25, 2017
    36d86b9
  6. added a commit that references this issue on Mar 7, 2017
    9f3f97d
  7. added a commit that references this issue on May 8, 2017
    b7abdab
  8. added a commit that references this issue on May 16, 2017
    7a11edd
  9. locked and limited conversation to collaborators on Jan 22, 2019
  10. added a commit that references this issue on Feb 24, 2019
    c715ff3
  11. added a commit that references this issue on Oct 8, 2024
    0f2d29c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions