{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/5253","labels_url":"https://api.github.com/repos/npm/npm/issues/5253/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/5253/comments","events_url":"https://api.github.com/repos/npm/npm/issues/5253/events","html_url":"https://github.com/npm/npm/issues/5253","id":33263902,"number":5253,"title":"suppress unnecessary npm WARN related to package.json fields","user":{"login":"timoxley","id":43438,"avatar_url":"https://avatars.githubusercontent.com/u/43438?v=3","gravatar_id":"","url":"https://api.github.com/users/timoxley","html_url":"https://github.com/timoxley","followers_url":"https://api.github.com/users/timoxley/followers","following_url":"https://api.github.com/users/timoxley/following{/other_user}","gists_url":"https://api.github.com/users/timoxley/gists{/gist_id}","starred_url":"https://api.github.com/users/timoxley/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timoxley/subscriptions","organizations_url":"https://api.github.com/users/timoxley/orgs","repos_url":"https://api.github.com/users/timoxley/repos","events_url":"https://api.github.com/users/timoxley/events{/privacy}","received_events_url":"https://api.github.com/users/timoxley/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/npm/npm/labels/feature-request","name":"feature-request","color":"ACE1AF"},{"url":"https://api.github.com/repos/npm/npm/labels/patch-welcome","name":"patch-welcome","color":"e102d8"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":17,"created_at":"2014-05-11T15:28:53Z","updated_at":"2015-11-19T09:26:02Z","closed_at":null,"body":"Under very few situations are the warnings reported by normalize-package-json actually useful, generally they are just noise, especially in the case that the warnings are for packages that are not under my control.\r\n\r\ne.g. during npm's own install procedure, these warnings are generated by 3rd party packages:\r\n```\r\nnpm WARN package.json github-url-from-git@1.1.1 No repository field.\r\nnpm WARN package.json ronn@0.3.8 'repositories' (plural) Not supported. Please pick one as the 'repository' field\r\n```\r\n\r\nThat is just noise, nobody needs to read that except the owners of those packages.\r\n\r\nI'm proposing one or more of the following:\r\n\r\n* default log level gets raised above warn\r\n* a config flag to specifically exclude warnings related to package.json\r\n* a config flag to specifically exclude warnings related to any package.json that is not the current package (i.e. `npm root`/../)\r\n* Raise package.json warnings for current package to errors that must be bypassed with --force on `npm publish` (or even during prepublish).\r\n\r\nWould be happy if these flags were on by default. Will PR if acceptable.\r\n\r\nRelated to https://github.com/npm/npm/issues/5213"},"comment":{"url":"https://api.github.com/repos/npm/npm/issues/comments/157999414","html_url":"https://github.com/npm/npm/issues/5253#issuecomment-157999414","issue_url":"https://api.github.com/repos/npm/npm/issues/5253","id":157999414,"user":{"login":"fbacker","id":4478361,"avatar_url":"https://avatars.githubusercontent.com/u/4478361?v=3","gravatar_id":"","url":"https://api.github.com/users/fbacker","html_url":"https://github.com/fbacker","followers_url":"https://api.github.com/users/fbacker/followers","following_url":"https://api.github.com/users/fbacker/following{/other_user}","gists_url":"https://api.github.com/users/fbacker/gists{/gist_id}","starred_url":"https://api.github.com/users/fbacker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fbacker/subscriptions","organizations_url":"https://api.github.com/users/fbacker/orgs","repos_url":"https://api.github.com/users/fbacker/repos","events_url":"https://api.github.com/users/fbacker/events{/privacy}","received_events_url":"https://api.github.com/users/fbacker/received_events","type":"User","site_admin":false},"created_at":"2015-11-19T09:26:02Z","updated_at":"2015-11-19T09:26:02Z","body":"Trying to use npm with Team Foundation Server to automatically manage builds. When running scripts (VNext) to install npm packages and Warnings appear it will cancel the build. I can continue with errors but the builds will get logged as partially succeeded that will confuse.\r\n\r\nSo seanmcilvenna idea of suppress isn't bad.\r\n    npm install --supress-warnings"}}