Development server not reachable from other computer in local network

[DavisOwen]

🐛 bug report

https://stackoverflow.com/questions/69262908/cant-access-parcel-js-development-server-on-another-machine

🤔 Expected Behavior

I should be able to reach the development server from my other machine at :1234

😯 Current Behavior

I am not receiving any connection from the other computer in network despite listening on port 1234 and being able to successfully ping the computer.

💁 Possible Solution

🔦 Context

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel
Node
npm/Yarn
Operating System

[mischnic]

This is by design (not exposing it by default). You can pass --host to listen on other addresses (for example --host 0.0.0.0 for everything, including localhost and your local IP)

[DavisOwen]

@mischnic Sorry I put more context in the stack overflow link I posted, as I'm asking the question there as well since it could be a networking issue (although im fairly certain it is an issue unique to parcel for reasons listed in the question).

But basically I tried using --host 0.0.0.0 as well and it did not change anything, as well as trying many different ports (some that I know work). I even verified that the node server is listening on port 1234 as expected yet I am still not receiving any connections and the connection is timing out

[devongovett]

I think by default it should be accessible. I regularly access parcel dev servers from other machines. Are you sure it's not a firewall or router setting?

[DavisOwen]

EDIT: I forgot that I am using the deprecated version of parcel, parcel-bundler 1.12.5. This is unavoidable for me and my project since I could not get the recent 2.0 versions of parcel to work because of this issue I was having with my Mac

#5046

which I could not resolve.

So, to be fair this could be an issue that the old deprecated version of parcel-bundler doesnt handle. However I still feel like this should be working...

@devongovett I'm fairly sure because I've tried on 2 different routers now and I can ping the ip just fine. I also have run a django app on the same port and can access that fine as well so it seems unique to parcel

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.