Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix: Handle error when running init without npm #9169

Merged
merged 1 commit into from Aug 30, 2017
Merged

Fix: Handle error when running init without npm #9169

merged 1 commit into from Aug 30, 2017

Commits on Aug 28, 2017

  1. Fix: Handle error when running init without npm 

    Modify fetchPeerDependencies() function in npm-util to retun null if the
npm process exited with an ENOENT error.
Modify installSyncSaveDev() function in npm-util to log an error message  if the
npm process exited with an ENOENT error.
Write new tests for fetchPeerDependencies() and installSyncSaveDev() to
cover these scenarios.
Modify the sync stub in other installSyncSaveDev() tests to return an object
more similar to the child_process object specified in the node.js docs,
to avoid undefined field errors.
    @GAumala
    GAumala committed Aug 28, 2017
    Configuration menu
    Copy the full SHA
    2589fa1 View commit details
    Browse the repository at this point in the history