Meteor 3 changes the default behavior of Meteor.absoluteUrl() about meteor

[ToyboxZach]

If we decide it shouldbe different between windows and others, IMO it should just be suggested to use ROOT_URL=127.0.0.1 when running on windows, instead of changing how the actual code runs. Having it be different would make it more annoying for our experience, if we ever got a developer who worked on windows.

[ToyboxZach]

Ah got it, didn't see that when I first looked at the changelog (its a pretty hefty change log and obviously not finished so understandable)

That phrasing does make me still feel like I could force ROOT_URL=http://localhost so could use some fixing up. Also there is a typo as the url would be 127.0.0.1 not 127.0.1

[Grubba27]

Yes, we did that change, primarily because there was an issue with using localhost, with Node 16 > in Windows, from what I recall. We will do a revision on this, maybe this should only change for Windows.

[ToyboxZach]

Ah got it. I am personally fine with it switching, it would just need to be explicitly mentioned in a changelog. And I think it is worth it being the same across all platforms.

At first glance it just seemed like an unnecessary change that was breaking our testing experience.

[Grubba27]

It is being mentioned in the changelog:

meteor/docs/generators/changelog/versions/3.0.md

Lines 367 to 371 in a8dbcd7

	- Async local storage was added to help deal with async methods.
	- Added `promiseEmmiter` to help with async methods.
	- Removed `fibers` from package.
	- `Meteor.absoluteUrl` in localhost uses `127.0.1` by default.

.

You gave me a good idea. Run the windows tests exactly like you said, passing the argument ROOT_URL.