GeezerVison is showing github.com — doc: clarify use of process.env in worker threads on Windows · nodejs/node@ead654f
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/process.md +3-1Lines changed: 3 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -1668,7 +1668,9 @@ each [`Worker`][] thread has its own copy of `process.env`, based on its |
1668 | 1668 | parent thread's `process.env`, or whatever was specified as the `env` option |
1669 | 1669 | to the [`Worker`][] constructor. Changes to `process.env` will not be visible |
1670 | 1670 | across [`Worker`][] threads, and only the main thread can make changes that |
1671 | | -are visible to the operating system or to native add-ons. |
| 1671 | +are visible to the operating system or to native add-ons. On Windows, a copy of |
| 1672 | +`process.env` on a [`Worker`][] instance operates in a case-sensitive manner |
| 1673 | +unlike the main thread. |
1672 | 1674 |
|
1673 | 1675 | ## `process.execArgv` |
1674 | 1676 |
|
|
Collapse file
Copy file name to clipboardExpand all lines: doc/api/worker_threads.md +2-1Lines changed: 2 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -844,7 +844,8 @@ Notable differences inside a Worker environment are: |
844 | 844 | unless otherwise specified. Changes to one copy are not visible in other |
845 | 845 | threads, and are not visible to native add-ons (unless |
846 | 846 | [`worker.SHARE_ENV`][] is passed as the `env` option to the |
847 | | - [`Worker`][] constructor). |
| 847 | + [`Worker`][] constructor). On Windows, unlike the main thread, a copy of the |
| 848 | + environment variables operates in a case-sensitive manner. |
848 | 849 | * [`process.title`][] cannot be modified. |
849 | 850 | * Signals are not delivered through [`process.on('...')`][Signals events]. |
850 | 851 | * Execution may stop at any point as a result of [`worker.terminate()`][] |
|