Skip to content

Conversation

devversion
Copy link
Member

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Feb 13, 2025
@devversion devversion force-pushed the experiment-windows branch 29 times, most recently from 3f1fcf5 to 9eaaafa Compare February 14, 2025 13:31
@devversion devversion force-pushed the experiment-windows branch 14 times, most recently from af1d2e2 to 14d9fd3 Compare February 20, 2025 18:31
…ble variant

When testing native Windows via WSL, the loopback address (localhost) is
not necessarily the correct one anymore.

NOTE: This is not needed for general development/testing inside WSL;
it's just needed because we still want to test native Windows on CI,
and launch powershell/cmd from inside WSL to simulate a real native
Windows CLI user experience.

Context on why this is needed: When spawning e.g. ng serve via CMD, the
process runs outside WSL, so `localhost`, when a test wants to assert the
served content, is not correct. Instead the NAT IP of the Windows host
needs to be used directly. This is what this change enables.

Notably WSL does have a mirrored networking mode, but it doesn't work
well. Requests from WSL to the Windows host typically fail with
connection refused errors (and there are many issues reported). The NAT
approach (default by WSL) is safer, and works, but is a little more work
as can be seen in this commit.
@devversion devversion force-pushed the experiment-windows branch 5 times, most recently from 85dbb8d to 19a94d3 Compare February 21, 2025 11:57
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area: build & ci Related the build and CI infrastructure of the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants