-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development Port doesn't auto-closes after failing of gatsby-develop #115
Comments
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. |
Thanks @bhayashi 😃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When a user is running
GatsbyHub
withoutyarn install
ornpm install
, GatsbyHub populates a preview that it has started running on port 8000 i.e. the default dev port as a result ofgatsby develop
but instantly fails. Until this part it's great, but thedevelopment 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 thedevelop
fails the port should also autoclose.To Reproduce
Steps to reproduce the behavior:
Screenshots
If required I can provide it in the comment section.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: