{"push_id":1301334859,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"f33cef9864feef6a1a8d09738921615855b9539e","before":"395f5304492c8525aeaa15f7fce8ae33d9d68e56","commits":[{"sha":"f33cef9864feef6a1a8d09738921615855b9539e","author":{"name":"Nicholas Pape","email":"5322a0e765306731ebbff46aeb9c3b04685e09ba@microsoft.com"},"message":"Remove the --global flag from README\n\nWe were curious about this, so I published a sample package with a dev dependency on something not in my globally installed folders (in %AppData% and Program Files) package.  I then ran npm install without that flag, and checked my global `node modules` folders.. \r\n\r\nReading the [NPM documentation](https://docs.npmjs.com/cli/install), it is unclear whether the `--production` flag applies to --global installs. Both flags are only documented under the \"(in package directory, no arguments)\" section, although `--global` obviously applies to other sections as well.\r\n\r\nFurthermore, NPM does very little argument parsing, you can even include non-existent flags, such as: `npm install -g --helloworld @microsoft/generator-sharepoint --microsoft`.\r\n\r\nThe main reason for bringing this up, is that in our project's README, we tell users to run `npm install -g --production windows-build-tools`, but we would prefer to not have this flag there if it has no effect.\r\n\r\nALSO, thanks for the great work on this project!","distinct":true,"url":"https://api.github.com/repos/nickpape-msft/windows-build-tools/commits/f33cef9864feef6a1a8d09738921615855b9539e"}]}
{"actor":{"display_login":"nickpape-msft"}}