fix(core): align inconsistent behavior of getEnv() and getEnvWithoutDefaults() when a process polyfill is used #4649
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
When running in a Browser and a
process
polyfill is used, getEnv() and getEnvWithoutDefaults() behave in different ways.getEnvWithoutDefaults()
will use the polyfilledprocess.env
andgetEnv()
will use_globalThis
. This aligns the behavior of both.The inconsistent behavior can lead to results where span-limits are configured differently based on if a polyfill is used or not. I'm not sure if anyone is actually using environment configuration via
_globalThis
, though. It feels to me like using this would be a weird choice for configuring things.Enables #4648, where we have to use a process polyfill to update to
karma-webpack@5.0.1
Type of change
How Has This Been Tested?