PROPOSAL: Fail on npm/node issues during buffalo new

[markbates]

The current behavior of buffalo new is to try and install the Webpack asset pipeline. If this fails, Buffalo falls back to trying to install the various missing pieces, but should all of that still fails, Buffalo issues a warning and moves on.

I argue that this causes many users bizarre and often confusing errors down the line that are difficult to track down.

I propose, that instead of a warning, we error instead. This raise the issue with the developer more directly and will the give them the chance to either a) install the proper missing/broken Webpack related infrastructure or b) let the re-run the command with the --skip-weback flag to build an application without the need for those tools.