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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the Repository Style Guide (Testing Conventions, lines 87-88), to "unset" an environment variable, we must use an empty string
vi.stubEnv('NAME', '')instead ofundefined.However, simply changing this to
vi.stubEnv('NO_PROXY', '')will cause this test to fail because the implementation inpackages/core/src/utils/fetch.tsuses the nullish coalescing operator (??):Since
''is not nullish, it won't fall back tono_proxy.To fix this and adhere to the style guide, and to ensure we trim the optional string and use the fallback if the result is empty (to avoid whitespace-only strings), please update the implementation in
packages/core/src/utils/fetch.tsto:And then update this test to use
vi.stubEnv('NO_PROXY', '').References
vi.stubEnv('NAME', ''). (link)