Svelte default port conflict with ASP.NET Core default port.

[Kuinox]

Is your feature request related to a problem? Please describe.
The problem is simple: out of the box, ASP.NET Core and Svelte both use port 5000.
This requires to configure one of them and it won't work out of the box.

Describe the solution you'd like
The solution is simple: the default should be something where it has less chance to conflict with a software used with svelte.

How important is this feature to you?
Not really important, I only want reduce friction in bootstraping a new app when you choose Svelte & ASP.NET Core.

[ceifa]

Maybe svelte should check if the port is taken, and if so, try to use the port 5001 and so on...

[Kuinox]

Taking a random port (which is current behavior) is better in case of conflict:
What if you start the svelte server before the ASP.NET Core server? Well, svelte will take the port 5000, but your front app is configured to hit... localhost:5000.

[antony]

I'm confused by this issue - Svelte doesn't have a default port. Svelte is a compiler which produces Javascript and CSS. Did you mean to open this in one of the template apps? As far as I know they will all use an alternate port if the one they want is taken, and it's usually port 3000, not 5000.

[Kuinox]

Yes sorry, I just checked, the template use sirv which default to port 5000.