Skip to content

Gracefully handle initial npm errors #1505

Closed
@gaearon

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.

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