{"action":"created","issue":{"url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/69","repository_url":"https://api.github.com/repos/pvorb/npm-stat.com","labels_url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/69/labels{/name}","comments_url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/69/comments","events_url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/69/events","html_url":"https://github.com/pvorb/npm-stat.com/issues/69","id":365244830,"node_id":"MDU6SXNzdWUzNjUyNDQ4MzA=","number":69,"title":"New packages cause error","user":{"login":"kanekotic","id":3071208,"node_id":"MDQ6VXNlcjMwNzEyMDg=","avatar_url":"https://avatars1.githubusercontent.com/u/3071208?v=4","gravatar_id":"","url":"https://api.github.com/users/kanekotic","html_url":"https://github.com/kanekotic","followers_url":"https://api.github.com/users/kanekotic/followers","following_url":"https://api.github.com/users/kanekotic/following{/other_user}","gists_url":"https://api.github.com/users/kanekotic/gists{/gist_id}","starred_url":"https://api.github.com/users/kanekotic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kanekotic/subscriptions","organizations_url":"https://api.github.com/users/kanekotic/orgs","repos_url":"https://api.github.com/users/kanekotic/repos","events_url":"https://api.github.com/users/kanekotic/events{/privacy}","received_events_url":"https://api.github.com/users/kanekotic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-30T17:43:39Z","updated_at":"2018-09-30T21:03:04Z","closed_at":null,"author_association":"NONE","body":"Packages that are too new will cause an error. As seen in the next image: \r\n\r\n<img width=\"538\" alt=\"screen shot 2018-09-30 at 19 40 49\" src=\"https://user-images.githubusercontent.com/3071208/46260633-c4528800-c4e8-11e8-9949-e3df7d7c5a80.png\">\r\n\r\nIs it possible to add a filter to the query for this cases? 🤔"},"comment":{"url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/comments/425751850","html_url":"https://github.com/pvorb/npm-stat.com/issues/69#issuecomment-425751850","issue_url":"https://api.github.com/repos/pvorb/npm-stat.com/issues/69","id":425751850,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNTc1MTg1MA==","user":{"login":"pvorb","id":183534,"node_id":"MDQ6VXNlcjE4MzUzNA==","avatar_url":"https://avatars3.githubusercontent.com/u/183534?v=4","gravatar_id":"","url":"https://api.github.com/users/pvorb","html_url":"https://github.com/pvorb","followers_url":"https://api.github.com/users/pvorb/followers","following_url":"https://api.github.com/users/pvorb/following{/other_user}","gists_url":"https://api.github.com/users/pvorb/gists{/gist_id}","starred_url":"https://api.github.com/users/pvorb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pvorb/subscriptions","organizations_url":"https://api.github.com/users/pvorb/orgs","repos_url":"https://api.github.com/users/pvorb/repos","events_url":"https://api.github.com/users/pvorb/events{/privacy}","received_events_url":"https://api.github.com/users/pvorb/received_events","type":"User","site_admin":false},"created_at":"2018-09-30T21:03:04Z","updated_at":"2018-09-30T21:03:04Z","author_association":"OWNER","body":"How could npm-stat tell the difference between packages that do not exist and packages that have no data yet? If your package is new you might be able to figure out the reason on your own, don't you think so?"}}
{"actor":{"display_login":"pvorb"}}