-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[release/8.0][wasm] Use intended ports when running DevServer
#92906
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
Conversation
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFor running a wasm-browser application
Fixes #88832 .
|
DevServerDevServer
|
Test failure is relevant. |
|
Approved by Tactics via email.
@radical ping me when the test failure is addressed so I can merge. I'll add the blocked label meanwhile. |
…mly select a port
|
@carlossanlop this is ready. |
For running a wasm-browser application
DevServeris used, but it always started the webserver on port5000, because the selected ports weren't used by theDevServer, and thus used the defaults.ASPNETCORE_URLS=''in the environment.Fixes #91143 .
Customer impact
Every run for a
wasmbrowsertemplate (which is still only in thewasm-experimentalworkload) will use a random port for the webserver, instead of a fixed5000, as intended.Testing
Automated testing.
Impact
Low. This affects an experimental feature.