{"action":"created","issue":{"url":"https://api.github.com/repos/zeit/now-cli/issues/1283","repository_url":"https://api.github.com/repos/zeit/now-cli","labels_url":"https://api.github.com/repos/zeit/now-cli/issues/1283/labels{/name}","comments_url":"https://api.github.com/repos/zeit/now-cli/issues/1283/comments","events_url":"https://api.github.com/repos/zeit/now-cli/issues/1283/events","html_url":"https://github.com/zeit/now-cli/issues/1283","id":312765074,"number":1283,"title":"Builds failing, but only indication is dashboard 'error' badge","user":{"login":"brandonmp","id":14139991,"avatar_url":"https://avatars2.githubusercontent.com/u/14139991?v=4","gravatar_id":"","url":"https://api.github.com/users/brandonmp","html_url":"https://github.com/brandonmp","followers_url":"https://api.github.com/users/brandonmp/followers","following_url":"https://api.github.com/users/brandonmp/following{/other_user}","gists_url":"https://api.github.com/users/brandonmp/gists{/gist_id}","starred_url":"https://api.github.com/users/brandonmp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brandonmp/subscriptions","organizations_url":"https://api.github.com/users/brandonmp/orgs","repos_url":"https://api.github.com/users/brandonmp/repos","events_url":"https://api.github.com/users/brandonmp/events{/privacy}","received_events_url":"https://api.github.com/users/brandonmp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2018-04-10T04:00:25Z","updated_at":"2018-04-13T04:31:51Z","closed_at":null,"author_association":"NONE","body":"Using `next@5.1` with `typescript@2.8` and `now@11.0.7` (have also tried `now@12.0.0-canary.5`)\r\n\r\nThe branch builds and runs locally (win 10, node 9 using bash for windows) in ~120 seconds with no errors. \r\n\r\nHowever, when deploying to `now`, the build hangs indefinitely on `next build`. \r\n\r\nThe only indication that something's gone wrong is in the `now.sh` dashboard, where the big red \"ERROR\" badge appears (usually within the first few minutes of deploying):\r\n\r\n![image](https://user-images.githubusercontent.com/14139991/38535206-7500120c-3c50-11e8-804c-380006ef58c8.png)\r\n\r\nBut the logs show no error (these are from `now.sh`, but they basically mirror my terminal): \r\n\r\n```\r\n04/09 11:43 PM (4m) install\r\n04/09 11:43 PM (4m) ✓ Using \"yarn.lock\"\r\n04/09 11:43 PM (4m) ⧗ Installing 89 main dependencies…\r\n04/09 11:43 PM (4m) npm run build\r\n```\r\nnote that my `build` script is simply `NODE_ENV=production next build`\r\n\r\n**But,** when I switch to my `master` branch and deploy, however, it builds fine. There aren't any architectual differences b/t the two branches (just a new route and some new components), so the build process is about the same.\r\n\r\nSo, I assume it's gotta be something in my code that's breaking the build, but I can't figure out why:\r\n\r\n(a)  it builds locally just fine\r\nor (b) there's no error message at all\r\n\r\nIs there anyway to debug this? or maybe more detailed logs available server-side? `now` should be printing some indication as to why it's failing, right?\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/zeit/now-cli/issues/comments/381020022","html_url":"https://github.com/zeit/now-cli/issues/1283#issuecomment-381020022","issue_url":"https://api.github.com/repos/zeit/now-cli/issues/1283","id":381020022,"user":{"login":"13806","id":31736960,"avatar_url":"https://avatars1.githubusercontent.com/u/31736960?v=4","gravatar_id":"","url":"https://api.github.com/users/13806","html_url":"https://github.com/13806","followers_url":"https://api.github.com/users/13806/followers","following_url":"https://api.github.com/users/13806/following{/other_user}","gists_url":"https://api.github.com/users/13806/gists{/gist_id}","starred_url":"https://api.github.com/users/13806/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/13806/subscriptions","organizations_url":"https://api.github.com/users/13806/orgs","repos_url":"https://api.github.com/users/13806/repos","events_url":"https://api.github.com/users/13806/events{/privacy}","received_events_url":"https://api.github.com/users/13806/received_events","type":"User","site_admin":false},"created_at":"2018-04-13T04:31:51Z","updated_at":"2018-04-13T04:31:51Z","author_association":"NONE","body":"Running` npm install` instead of `yarn install` at npm v5.3.0 fixes this one for me."}}
{"actor":{"display_login":"13806"}}