doc: clarify use of process.env in worker threads on Windows#49008
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Aug 5, 2023
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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.
A worker thread uses a copy of parent thread's
process.envby default. The current document explains differences caused by the copy, but it doesn't cover the case sensitivity difference on Windows.This patch updates the document in this regard.
Fixes: #48955
Alternative to #48976
Signed-off-by: Daeyeon Jeong [email protected]