gatsby: develop command crashing when default 8000 port in use,

I’ve bumped into a bug only in the last day or two and I’m not sure what update might have caused the change. When running npx gatsby develop and I already have something running on port 8000, I’d get the standard response: Would you like to run the app at another port instead? but now the command crashes.

I can still run my server on another port with npx gatsby develop -p 8001 and I so far assume this issue won’t interfere with anything else. I’ve not found this specific bug reported but there does appear to be recent activity around other yoga-layout-prebuilt bugs… Here’s the error:

/Users/Antonio/code/gatsby-starter-blog/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: listen EADDRINUSE: address already in use :::8000
    at Server.setupListenHandle [as _listen2] (net.js:1313:16)
    at listenInCluster (net.js:1361:12)
    at Server.listen (net.js:1447:7)
    at startDevelopProxy (/Users/Antonio/code/gatsby-starter-blog/node_modules/gatsby/dist/utils/develop-proxy.js:79:10)
    at module.exports (/Users/Antonio/code/gatsby-starter-blog/node_modules/gatsby/dist/commands/develop.js:133:53)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1340:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EADDRINUSE',
  errno: -48,
  syscall: 'listen',
  address: '::',
  port: 8000
}