Why not `localhost:3000`? about serve

[timneutkens]

Might help to mitigate your issue: serve -p 3000

[derhuerst]

Also, running on a random port means that every time you restart, you can't just refresh your browser -- you have to paste in the new address.

You'd usually keep this server running, while your code bundler/build system will rebuild your bundles.

[leo]

Exactly! @derhuerst @timneutkens 😊

[ericsoco]

@derhuerst yes, but sometimes you need to restart...it's a minor ergonomic issue, just wondering about the reasoning behind the change.

@timneutkens I already added that to my npm script, again just wondering why the setup here is different than in the previous version of serve (pre 2.0). It amounts to an API change, essentially. I can adapt, just wondering why @leo et al. didn't try to maintain the previous workflow.

[derhuerst]

yes, but sometimes you need to restart

when?

it's a minor ergonomic issue, just wondering about the reasoning behind the change.

Using random ports is in many cases very sensible, as starting the server would usually fail binding a port already used. From what it seems, the setup at now.sh is geared towards random ports.

[ericsoco]

@derhuerst when I make changes to files that are not watched; when my watcher doesn't catch changes due to setup omissions; when i restart my computer and Chrome reopens tabs. It's not common but it's not a fabricated scenario, either.

Interesting you mention failing binding to a port already in use. I had a conflict on port 3000 as I was trying to get serve working, in fact. However, serve seems to fail silently in this case -- the console shows no indication the port is in use. Can open a separate issue if that is actually a bug. Thanks for the now.sh example, makes sense.

[derhuerst]

However, serve seems to fail silently in this case -- the console shows no indication the port is in use. Can open a separate issue if that is actually a bug.

Cannot confirm on master.

[ericsoco]

@derhuerst just tested again and now I see an EADDRINUSE error, so feel free to ignore :D