{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/5253","repository_url":"https://api.github.com/repos/npm/npm","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":"98DCFF"},{"url":"https://api.github.com/repos/npm/npm/labels/patch-welcome","name":"patch-welcome","color":"BEEB71"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":27,"created_at":"2014-05-11T15:28:53Z","updated_at":"2016-06-15T16:20:36Z","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/226240418","html_url":"https://github.com/npm/npm/issues/5253#issuecomment-226240418","issue_url":"https://api.github.com/repos/npm/npm/issues/5253","id":226240418,"user":{"login":"JemiloII","id":5192788,"avatar_url":"https://avatars.githubusercontent.com/u/5192788?v=3","gravatar_id":"","url":"https://api.github.com/users/JemiloII","html_url":"https://github.com/JemiloII","followers_url":"https://api.github.com/users/JemiloII/followers","following_url":"https://api.github.com/users/JemiloII/following{/other_user}","gists_url":"https://api.github.com/users/JemiloII/gists{/gist_id}","starred_url":"https://api.github.com/users/JemiloII/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JemiloII/subscriptions","organizations_url":"https://api.github.com/users/JemiloII/orgs","repos_url":"https://api.github.com/users/JemiloII/repos","events_url":"https://api.github.com/users/JemiloII/events{/privacy}","received_events_url":"https://api.github.com/users/JemiloII/received_events","type":"User","site_admin":false},"created_at":"2016-06-15T16:20:36Z","updated_at":"2016-06-15T16:20:36Z","body":"Is this still an issue that needs a pr or is it a won't patch thing? Kinda about to just fork npm so I can get rid of annoying warnings and other things. Like I don't care if a package fails to build with node-gyp if the package is just going to use a binary. I'd rather just have an option to use the binary honestly. Speed up the install times if you know the binary just works out of the box. Deprecation warnings, I don't care for those in production logs. I just want to have useful warnings and errors, not clutter. Sorry if this post sounds as if its coming off strong, don't mean it to be, just pointing out nuisances in npm logging and lack of disabling some of the logging."}}
{"actor":{"display_login":"JemiloII"}}