{"action":"created","issue":{"url":"https://api.github.com/repos/getify/JSON.minify/issues/32","labels_url":"https://api.github.com/repos/getify/JSON.minify/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/getify/JSON.minify/issues/32/comments","events_url":"https://api.github.com/repos/getify/JSON.minify/issues/32/events","html_url":"https://github.com/getify/JSON.minify/issues/32","id":115955435,"number":32,"title":"exports doesn't work for node 5 in node-json-minify","user":{"login":"fuzing","id":11649301,"avatar_url":"https://avatars.githubusercontent.com/u/11649301?v=3","gravatar_id":"","url":"https://api.github.com/users/fuzing","html_url":"https://github.com/fuzing","followers_url":"https://api.github.com/users/fuzing/followers","following_url":"https://api.github.com/users/fuzing/following{/other_user}","gists_url":"https://api.github.com/users/fuzing/gists{/gist_id}","starred_url":"https://api.github.com/users/fuzing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fuzing/subscriptions","organizations_url":"https://api.github.com/users/fuzing/orgs","repos_url":"https://api.github.com/users/fuzing/repos","events_url":"https://api.github.com/users/fuzing/events{/privacy}","received_events_url":"https://api.github.com/users/fuzing/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-11-09T20:10:41Z","updated_at":"2015-11-12T15:05:45Z","closed_at":null,"body":"\r\nHi Kyle:\r\n\r\nCould you change the 'exports' to 'module.exports' so that it continues to work correctly in node-5.\r\n\r\nCheers,\r\n\r\nPB\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/getify/JSON.minify/issues/comments/156132281","html_url":"https://github.com/getify/JSON.minify/issues/32#issuecomment-156132281","issue_url":"https://api.github.com/repos/getify/JSON.minify/issues/32","id":156132281,"user":{"login":"pradyunsg","id":3275593,"avatar_url":"https://avatars.githubusercontent.com/u/3275593?v=3","gravatar_id":"","url":"https://api.github.com/users/pradyunsg","html_url":"https://github.com/pradyunsg","followers_url":"https://api.github.com/users/pradyunsg/followers","following_url":"https://api.github.com/users/pradyunsg/following{/other_user}","gists_url":"https://api.github.com/users/pradyunsg/gists{/gist_id}","starred_url":"https://api.github.com/users/pradyunsg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pradyunsg/subscriptions","organizations_url":"https://api.github.com/users/pradyunsg/orgs","repos_url":"https://api.github.com/users/pradyunsg/repos","events_url":"https://api.github.com/users/pradyunsg/events{/privacy}","received_events_url":"https://api.github.com/users/pradyunsg/received_events","type":"User","site_admin":false},"created_at":"2015-11-12T15:05:45Z","updated_at":"2015-11-12T15:05:45Z","body":"@fuzing It wasn't the fix, but the fact that the PR was targeted at the wrong branch in the repository that was the issue.\r\n\r\nThe repository had been recently re-organized, which broke the node-module. I should have made it more clear in my comment on the relavant PR. The fact that the re-organization wasn't documented well (or at all?) did not help the situation either.\r\n\r\nSo, I guess I should apologize for being overly terse in the relavant PR comment.\r\n\r\nLesson Learnt: Be less terse with PR comments.\r\n"}}