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.

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

Windows npm issues #159

Merged
merged 1 commit into from
Jan 5, 2017
Merged

Windows npm issues #159

merged 1 commit into from
Jan 5, 2017

Commits on Dec 25, 2016

  1. Run npm with --silent to prevent it from stalling on Windows

    For some reason, node-gyp never exits if we run `npm` commands without
    the `--silent` option. Passing `--no-progress --no-color` and/or
    capturing the output of stderr and stdout doesn't help.
    
    This will still make the npm commands fail in case something goes wrong,
    and won't suppress the node-gyp output when running cargo in verbose
    mode.
    Antonio Scandurra authored and Dave Herman committed Dec 25, 2016
    Configuration menu
    Copy the full SHA
    97822b3 View commit details
    Browse the repository at this point in the history