Development Port doesn't auto-closes after failing of gatsby-develop

[Neilblaze]

Describe the bug

When a user is running GatsbyHub without yarn install or npm install, GatsbyHub populates a preview that it has started running on port 8000 i.e. the default dev port as a result of gatsby develop but instantly fails. Until this part it's great, but the development port i.e. port 8000 should also autoclose with that failing instance with the ERR msg. The port is kept open until VSCode is restarted. This should be fixed. I think it requires a conditional check if the develop fails the port should also autoclose.

To Reproduce
Steps to reproduce the behavior:

1. Open any Gatsby starter file without npm or yarn pre-installed.
2. Click on 'GatsbyHub'
3. Look at "GatsbyHub" button on the VSC footer.
4. See error!

Screenshots

If required I can provide it in the comment section.

Desktop (please complete the following information):

• OS: Windows, Ubuntu LTS
• Browser : Chrome, Firefox

[bhashbrown]

Hi Neil, thanks for alerting us of this!

We're aware of this issue and we'll look at some ways of fixing it.

In the meantime, you can dispose the server by clicking the 'GatsbyHub' status bar icon or by clicking the 'circle-cross' icon on the 'Commands' menu without needing to restart VS Code.

[Neilblaze]

Thanks @bhayashi 😃