{"action":"created","issue":{"url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/11","labels_url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/11/comments","events_url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/11/events","html_url":"https://github.com/ForbesLindesay/spawn-sync/issues/11","id":58571267,"number":11,"title":"npm install doesn't work ","user":{"login":"edi9999","id":2071336,"avatar_url":"https://avatars.githubusercontent.com/u/2071336?v=3","gravatar_id":"","url":"https://api.github.com/users/edi9999","html_url":"https://github.com/edi9999","followers_url":"https://api.github.com/users/edi9999/followers","following_url":"https://api.github.com/users/edi9999/following{/other_user}","gists_url":"https://api.github.com/users/edi9999/gists{/gist_id}","starred_url":"https://api.github.com/users/edi9999/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/edi9999/subscriptions","organizations_url":"https://api.github.com/users/edi9999/orgs","repos_url":"https://api.github.com/users/edi9999/repos","events_url":"https://api.github.com/users/edi9999/events{/privacy}","received_events_url":"https://api.github.com/users/edi9999/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-02-23T11:01:15Z","updated_at":"2015-05-12T15:52:07Z","closed_at":null,"body":"Since spawn-sync v1.0.5, they is an error in  npm install : \r\n\r\n```\r\n> spawn-sync@1.0.5 postinstall /usr/local/lib/node_modules/clients-cli/node_modules/spawn-sync\r\n> node postinstall\r\n\r\n\r\n/usr/local/lib/node_modules/clients-cli/node_modules/spawn-sync/postinstall.js:38\r\n      throw err;\r\n            ^\r\nError: Command failed: npm ERR! Linux 3.16.0-30-generic\r\nnpm ERR! argv \"node\" \"/usr/local/bin/npm\" \"install\" \"--production\"\r\nnpm ERR! node v0.10.31\r\nnpm ERR! npm  v2.1.17\r\n\r\nnpm ERR! Uncaught, unspecified \"error\" event.\r\nnpm ERR!\r\nnpm ERR! If you need help, you may report this error at:\r\nnpm ERR!     <http://github.com/npm/npm/issues>\r\n\r\nnpm ERR! Please include the following file with any support request:\r\nnpm ERR!     /usr/local/lib/node_modules/clients-cli/node_modules/spawn-sync/npm-debug.log\r\n\r\n    at ChildProcess.exithandler (child_process.js:648:15)\r\n    at ChildProcess.emit (events.js:98:17)\r\n    at maybeClose (child_process.js:756:16)\r\n    at Process.ChildProcess._handle.onexit (child_process.js:823:5)\r\nnpm ERR! Linux 3.16.0-30-generic\r\nnpm ERR! argv \"node\" \"/usr/local/bin/npm\" \"install\" \".\" \"-g\"\r\nnpm ERR! node v0.10.31\r\nnpm ERR! npm  v2.1.17\r\nnpm ERR! code ELIFECYCLE\r\n\r\nnpm ERR! spawn-sync@1.0.5 postinstall: `node postinstall`\r\nnpm ERR! Exit status 8\r\nnpm ERR!\r\nnpm ERR! Failed at the spawn-sync@1.0.5 postinstall script 'node postinstall'.\r\nnpm ERR! This is most likely a problem with the spawn-sync package,\r\nnpm ERR! not with npm itself.\r\nnpm ERR! Tell the author that this fails on your system:\r\nnpm ERR!     node postinstall\r\nnpm ERR! You can get their info via:\r\nnpm ERR!     npm owner ls spawn-sync\r\nnpm ERR! There is likely additional logging output above.\r\n```\r\n\r\nThe error doesn't occur on 1.0.2"},"comment":{"url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/comments/101328731","html_url":"https://github.com/ForbesLindesay/spawn-sync/issues/11#issuecomment-101328731","issue_url":"https://api.github.com/repos/ForbesLindesay/spawn-sync/issues/11","id":101328731,"user":{"login":"akoval","id":2201456,"avatar_url":"https://avatars.githubusercontent.com/u/2201456?v=3","gravatar_id":"","url":"https://api.github.com/users/akoval","html_url":"https://github.com/akoval","followers_url":"https://api.github.com/users/akoval/followers","following_url":"https://api.github.com/users/akoval/following{/other_user}","gists_url":"https://api.github.com/users/akoval/gists{/gist_id}","starred_url":"https://api.github.com/users/akoval/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/akoval/subscriptions","organizations_url":"https://api.github.com/users/akoval/orgs","repos_url":"https://api.github.com/users/akoval/repos","events_url":"https://api.github.com/users/akoval/events{/privacy}","received_events_url":"https://api.github.com/users/akoval/received_events","type":"User","site_admin":false},"created_at":"2015-05-12T15:52:07Z","updated_at":"2015-05-12T15:52:07Z","body":"to avoid such problems in the future - try to freeze all you versions.\r\n\r\n1) npm shrinkwrap (in new npm 3 it will be better to use)\r\n2) commit all your dependencies in your repo and clear all package.json with \r\n*, ~, ^ in library versions (our private repo). Using such wildcards is bad practice. In my project we used library which has:\r\n\r\nspawn-sync: ^1.0.1\r\n\r\nSo latest MINOR update broke everything:)"}}