{"action":"closed","issue":{"url":"https://api.github.com/repos/OmniSharp/omnisharp-atom/issues/784","repository_url":"https://api.github.com/repos/OmniSharp/omnisharp-atom","labels_url":"https://api.github.com/repos/OmniSharp/omnisharp-atom/issues/784/labels{/name}","comments_url":"https://api.github.com/repos/OmniSharp/omnisharp-atom/issues/784/comments","events_url":"https://api.github.com/repos/OmniSharp/omnisharp-atom/issues/784/events","html_url":"https://github.com/OmniSharp/omnisharp-atom/issues/784","id":162335682,"number":784,"title":"Unable to install omnisharp-atom@0.3.0","user":{"login":"VintageXP","id":20147779,"avatar_url":"https://avatars.githubusercontent.com/u/20147779?v=3","gravatar_id":"","url":"https://api.github.com/users/VintageXP","html_url":"https://github.com/VintageXP","followers_url":"https://api.github.com/users/VintageXP/followers","following_url":"https://api.github.com/users/VintageXP/following{/other_user}","gists_url":"https://api.github.com/users/VintageXP/gists{/gist_id}","starred_url":"https://api.github.com/users/VintageXP/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/VintageXP/subscriptions","organizations_url":"https://api.github.com/users/VintageXP/orgs","repos_url":"https://api.github.com/users/VintageXP/repos","events_url":"https://api.github.com/users/VintageXP/events{/privacy}","received_events_url":"https://api.github.com/users/VintageXP/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-06-26T16:37:56Z","updated_at":"2016-06-30T22:00:44Z","closed_at":"2016-06-30T22:00:44Z","body":"`apm install omnisharp-atom@0.30.0` gives the following error:\r\n\r\n> spawn-sync@1.0.15 postinstall C:\\Users\\VINTAG~1\\AppData\\Local\\Temp\\apm-install-dir-116527->6920-18kw987\\node_modules\\omnisharp-atom\\node_modules\\generator->aspnet\\node_modules\\yeoman-generator\\node_modules\\yeoman->environment\\node_modules\\inquirer\\node_modules\\external-editor\\node_modules\\spawn-sync\r\n> node postinstall\r\n>\r\n>\r\n>npm WARN engine omnisharp-client@5.0.11: wanted: {\"node\":\">=0.12.0\",\"iojs\":\">=1.0.0\",\"atom\":\">=0.194.0\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\n>npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest >version of pug instead of jade\r\n>npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it >in the tree.\r\n>npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a >RegExp DoS issue\r\n>npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a >RegExp DoS issue\r\n>npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a >RegExp DoS issue\r\n>npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to >lodash@^4.0.0.\r\n>npm WARN engine deep-extend@0.4.1: wanted: {\"node\":\">=0.12.0\",\"iojs\":\">=1.0.0\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\n>npm WARN engine deep-extend@0.4.1: wanted: {\"node\":\">=0.12.0\",\"iojs\":\">=1.0.0\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\n>npm WARN engine escodegen@1.8.0: wanted: {\"node\":\">=0.12.0\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\n>npm WARN engine is-buffer@1.1.3: wanted: {\"node\":\">=0.12\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\n>npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.\r\nnpm WARN engine deep-extend@0.4.1: wanted: {\"node\":\">=0.12.0\",\"iojs\":\">=1.0.0\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine is-buffer@1.1.3: wanted: {\"node\":\">=0.12\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress-unzip@4.0.1: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress-targz@4.0.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress@4.0.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine strip-bom@3.0.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress-tar@4.1.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress-tar@4.1.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine decompress-tarbz2@4.1.0: wanted: {\"node\":\">=4\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm WARN engine is-buffer@1.1.3: wanted: {\"node\":\">=0.12\"} (current: {\"node\":\"0.10.40\",\"npm\":\"2.13.3\"})\r\nnpm ERR! Windows_NT 6.1.7601\r\nnpm ERR! argv \"C:\\\\Users\\\\VintageXP\\\\AppData\\\\Local\\\\atom\\\\app-1.8.0\\\\resources\\\\app\\\\apm\\\\bin\\\\node.exe\" \"C:\\\\Users\\\\VintageXP\\\\AppData\\\\Local\\\\atom\\\\app-1.8.0\\\\resources\\\\app\\\\apm\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js\" \"--globalconfig\" \"C:\\\\Users\\\\VintageXP\\\\.atom\\\\.apm\\\\.apmrc\" \"--userconfig\" \"C:\\\\Users\\\\VintageXP\\\\.atom\\\\.apmrc\" \"install\" \"C:\\\\Users\\\\VINTAG~1\\\\AppData\\\\Local\\\\Temp\\\\d-116527-6920-1fng2l6\\\\package.tgz\" \"--target=0.36.8\" \"--arch=ia32\"\r\nnpm ERR! node v0.10.40\r\nnpm ERR! npm  v2.13.3\r\nnpm ERR! file C:\\Windows\\system32\\cmd.exe\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! errno ENOENT\r\nnpm ERR! syscall spawn\r\n\r\n>npm ERR! spawn-sync@1.0.15 postinstall: `node postinstall`\r\n>npm ERR! spawn ENOENT\r\n>npm ERR! \r\n>npm ERR! Failed at the spawn-sync@1.0.15 postinstall script 'node postinstall'.\r\n>npm ERR! This is most likely a problem with the spawn-sync package,\r\n>npm ERR! not with npm itself.\r\n>npm ERR! Tell the author that this fails on your system:\r\n>npm ERR!     node postinstall\r\n>npm ERR! You can get their info via:\r\n>npm ERR!     npm owner ls spawn-sync\r\n>npm ERR! There is likely additional logging output above."}}
{"actor":{"display_login":"VintageXP"}}