{"action":"created","issue":{"url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/303","repository_url":"https://api.github.com/repos/SBoudrias/Inquirer.js","labels_url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/303/labels{/name}","comments_url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/303/comments","events_url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/303/events","html_url":"https://github.com/SBoudrias/Inquirer.js/issues/303","id":116952332,"number":303,"title":"Arrow keys for selecting options doesn't work in Windows","user":{"login":"nmai","id":4383203,"avatar_url":"https://avatars.githubusercontent.com/u/4383203?v=3","gravatar_id":"","url":"https://api.github.com/users/nmai","html_url":"https://github.com/nmai","followers_url":"https://api.github.com/users/nmai/followers","following_url":"https://api.github.com/users/nmai/following{/other_user}","gists_url":"https://api.github.com/users/nmai/gists{/gist_id}","starred_url":"https://api.github.com/users/nmai/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nmai/subscriptions","organizations_url":"https://api.github.com/users/nmai/orgs","repos_url":"https://api.github.com/users/nmai/repos","events_url":"https://api.github.com/users/nmai/events{/privacy}","received_events_url":"https://api.github.com/users/nmai/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-11-14T21:13:22Z","updated_at":"2016-06-02T20:55:18Z","closed_at":"2015-11-14T22:15:56Z","body":"This issue is directly related: https://github.com/eslint/eslint/issues/3880\r\n\r\nPressing the arrow keys does nothing. Running node.js v4.1.2 under Windows 8.1."},"comment":{"url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/comments/223419409","html_url":"https://github.com/SBoudrias/Inquirer.js/issues/303#issuecomment-223419409","issue_url":"https://api.github.com/repos/SBoudrias/Inquirer.js/issues/303","id":223419409,"user":{"login":"jokeyrhyme","id":479816,"avatar_url":"https://avatars.githubusercontent.com/u/479816?v=3","gravatar_id":"","url":"https://api.github.com/users/jokeyrhyme","html_url":"https://github.com/jokeyrhyme","followers_url":"https://api.github.com/users/jokeyrhyme/followers","following_url":"https://api.github.com/users/jokeyrhyme/following{/other_user}","gists_url":"https://api.github.com/users/jokeyrhyme/gists{/gist_id}","starred_url":"https://api.github.com/users/jokeyrhyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jokeyrhyme/subscriptions","organizations_url":"https://api.github.com/users/jokeyrhyme/orgs","repos_url":"https://api.github.com/users/jokeyrhyme/repos","events_url":"https://api.github.com/users/jokeyrhyme/events{/privacy}","received_events_url":"https://api.github.com/users/jokeyrhyme/received_events","type":"User","site_admin":false},"created_at":"2016-06-02T20:55:18Z","updated_at":"2016-06-02T20:55:18Z","body":"I have a module that helps identify broken versions of Node:\r\n\r\n- https://github.com/jokeyrhyme/is-node-interactive-tty-broken\r\n\r\nDo you think it might be worth integrating a similar check into this library? So that a warning or something could be displayed? Or perhaps modifying the \"engines\" part of package.json to help avoid broken Node versions at installation time?"}}
{"actor":{"display_login":"jokeyrhyme"}}