Commit 1c61418
doc: simplify recommendations in process.md
Remove recommendation that has no explanation. Make the other
recommendation less wordy.
PR-URL: #42556
Reviewed-By: Mestery <mestery@protonmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com>1 parent 2565090 commit 1c61418
1 file changed
Lines changed: 2 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -7,8 +7,7 @@ | |||
| 7 | 7 | <!-- source_link=lib/process.js --> | |
| 8 | 8 | ||
| 9 | 9 | The `process` object provides information about, and control over, the current | |
| 10 | - Node.js process. While it is available as a global, it is recommended to | ||
| 11 | - explicitly access it via require or import: | ||
| 10 | + Node.js process. | ||
| 12 | 11 | ||
| 13 | 12 | ```mjs | |
| 14 | 13 | import process from 'process'; | |
@@ -1487,8 +1486,7 @@ The following additional handling is implemented if the warning `type` is | |||
| 1487 | 1486 | ### Avoiding duplicate warnings | |
| 1488 | 1487 | ||
| 1489 | 1488 | As a best practice, warnings should be emitted only once per process. To do | |
| 1490 | - so, it is recommended to place the `emitWarning()` behind a simple boolean | ||
| 1491 | - flag as illustrated in the example below: | ||
| 1489 | + so, place the `emitWarning()` behind a boolean. | ||
| 1492 | 1490 | ||
| 1493 | 1491 | ```mjs | |
| 1494 | 1492 | import { emitWarning } from 'process'; | |
0 commit comments