Issue with automatic port forwarding in GitHub code spaces after upgrading to Gatsby 5

schettn commented 1 year ago

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
[X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

Before upgrading to Gatsby 5, I was able to use GitHub Codespaces and the port was automatically forwarded, allowing me to access my site without any additional configuration. However, after upgrading to Gatsby 5, I noticed that I can no longer access my site without specifying the gatsby develop -H 0.0.0.0 command instead of just gatsby develop.

I'm wondering if this change was intentional or if it's a bug.

Steps to Reproduce

Create a new GitHub code space
Install Gatsby 5
Start a Gatsby develop server using Gatsby develop
Try to access the site from the code space's browser preview or by navigating to the appropriate URL

Expected Result

The site should load without any additional configuration needed.

Actual Result

The site does not load, and I receive an error message indicating that the server could not be reached.

Additional information

I did not have to specify the -h flag with previous versions of Gatsby, and it seems like this change may have broken the automatic port forwarding in GitHub code spaces. Any insight or assistance would be greatly appreciated.

EyaChebbi commented 1 year ago

Hello is anyone working on this right now ?

limistah commented 1 year ago

I am unable to reproduce this.

Steps followed:

Setup a new gatsby(^5.12.0) project on codespaces
run gatsby develop
Use the preview either by the URL or by the preview tab.

Let me know if I am missing something

gatsbyjs / gatsby