If those work but the ember s command with same ports does work, let me know. So - how to solve this problem - i will think about it - windows 10 has an un-related issue where it allows over-taking an already in use port + host - which means there may be a 2 birds w/ one stone approach here - either way, if portfinder fails on macOS with touchbar, the issue becomes more serious (b/c most of us use mac.
NOTE - this is likely the issue, or the issue is related in nature to this 'way of checking' for an open port You can manually produce this error by running ember s w/ 2 different addons at the same time(with very little luck needed)ī) b/c portfinder checks for an open port by listening on the port+host, but does not actually send anything through the socket, its possible macOS is allowing a socket connection, but throws when sending data through - which throws a node syserr, which is caught and re-thrown as the above generic error - i've tried sending data through but it fails if bluetooth is enabled(for example), so had to revert that idea. Without any new knowledge, or debugging, this means thatĪ) between the time portfinder checked to see if that port was open and when livereload started on the same port(there is a real delay here, perhaps 1s), the port became in use. Livereload failed on It is either in use or you do not have permission.
