@@ -129,7 +129,7 @@ exec('"my script.cmd" a b', (err, stdout, stderr) => { |
129 | 129 | }); |
130 | 130 | ``` |
131 | 131 |
|
132 | | -### child_process.exec(command\[, options\]\[, callback\]) |
| 132 | +### `child_process.exec(command[, options][, callback])` |
133 | 133 | <!-- YAML |
134 | 134 | added: v0.1.90 |
135 | 135 | changes: |
@@ -233,7 +233,7 @@ async function lsExample() { |
233 | 233 | lsExample(); |
234 | 234 | ``` |
235 | 235 |
|
236 | | -### child_process.execFile(file\[, args\]\[, options\]\[, callback\]) |
| 236 | +### `child_process.execFile(file[, args][, options][, callback])` |
237 | 237 | <!-- YAML |
238 | 238 | added: v0.1.91 |
239 | 239 | changes: |
@@ -317,7 +317,7 @@ getVersion(); |
317 | 317 | function. Any input containing shell metacharacters may be used to trigger |
318 | 318 | arbitrary command execution.** |
319 | 319 |
|
320 | | -### child_process.fork(modulePath\[, args\]\[, options\]) |
| 320 | +### `child_process.fork(modulePath[, args][, options])` |
321 | 321 | <!-- YAML |
322 | 322 | added: v0.5.0 |
323 | 323 | changes: |
@@ -382,7 +382,7 @@ current process. |
382 | 382 | The `shell` option available in [`child_process.spawn()`][] is not supported by |
383 | 383 | `child_process.fork()` and will be ignored if set. |
384 | 384 |
|
385 | | -### child_process.spawn(command\[, args\]\[, options\]) |
| 385 | +### `child_process.spawn(command[, args][, options])` |
386 | 386 | <!-- YAML |
387 | 387 | added: v0.1.90 |
388 | 388 | changes: |
@@ -523,7 +523,7 @@ Node.js currently overwrites `argv[0]` with `process.execPath` on startup, so |
523 | 523 | parameter passed to `spawn` from the parent, retrieve it with the |
524 | 524 | `process.argv0` property instead. |
525 | 525 |
|
526 | | -#### options.detached |
| 526 | +#### `options.detached` |
527 | 527 | <!-- YAML |
528 | 528 | added: v0.7.10 |
529 | 529 | --> |
@@ -581,7 +581,7 @@ const subprocess = spawn('prg', [], { |
581 | 581 | subprocess.unref(); |
582 | 582 | ``` |
583 | 583 |
|
584 | | -#### options.stdio |
| 584 | +#### `options.stdio` |
585 | 585 | <!-- YAML |
586 | 586 | added: v0.7.10 |
587 | 587 | changes: |
@@ -686,7 +686,7 @@ Blocking calls like these are mostly useful for simplifying general-purpose |
686 | 686 | scripting tasks and for simplifying the loading/processing of application |
687 | 687 | configuration at startup. |
688 | 688 |
|
689 | | -### child_process.execFileSync(file\[, args\]\[, options\]) |
| 689 | +### `child_process.execFileSync(file[, args][, options])` |
690 | 690 | <!-- YAML |
691 | 691 | added: v0.11.12 |
692 | 692 | changes: |
@@ -753,7 +753,7 @@ If the process times out or has a non-zero exit code, this method will throw an |
753 | 753 | function. Any input containing shell metacharacters may be used to trigger |
754 | 754 | arbitrary command execution.** |
755 | 755 |
|
756 | | -### child_process.execSync(command\[, options\]) |
| 756 | +### `child_process.execSync(command[, options])` |
757 | 757 | <!-- YAML |
758 | 758 | added: v0.11.12 |
759 | 759 | changes: |
@@ -813,7 +813,7 @@ The [`Error`][] object will contain the entire result from |
813 | 813 | **Never pass unsanitized user input to this function. Any input containing shell |
814 | 814 | metacharacters may be used to trigger arbitrary command execution.** |
815 | 815 |
|
816 | | -### child_process.spawnSync(command\[, args\]\[, options\]) |
| 816 | +### `child_process.spawnSync(command[, args][, options])` |
817 | 817 | <!-- YAML |
818 | 818 | added: v0.11.12 |
819 | 819 | changes: |
@@ -890,7 +890,7 @@ exited. |
890 | 890 | function. Any input containing shell metacharacters may be used to trigger |
891 | 891 | arbitrary command execution.** |
892 | 892 |
|
893 | | -## Class: ChildProcess |
| 893 | +## Class: `ChildProcess` |
894 | 894 | <!-- YAML |
895 | 895 | added: v2.2.0 |
896 | 896 | --> |
@@ -904,7 +904,7 @@ use the [`child_process.spawn()`][], [`child_process.exec()`][], |
904 | 904 | [`child_process.execFile()`][], or [`child_process.fork()`][] methods to create |
905 | 905 | instances of `ChildProcess`. |
906 | 906 |
|
907 | | -### Event: 'close' |
| 907 | +### Event: `'close'` |
908 | 908 | <!-- YAML |
909 | 909 | added: v0.7.7 |
910 | 910 | --> |
@@ -933,7 +933,7 @@ ls.on('exit', (code) => { |
933 | 933 | }); |
934 | 934 | ``` |
935 | 935 |
|
936 | | -### Event: 'disconnect' |
| 936 | +### Event: `'disconnect'` |
937 | 937 | <!-- YAML |
938 | 938 | added: v0.7.2 |
939 | 939 | --> |
@@ -944,7 +944,7 @@ The `'disconnect'` event is emitted after calling the |
944 | 944 | possible to send or receive messages, and the [`subprocess.connected`][] |
945 | 945 | property is `false`. |
946 | 946 |
|
947 | | -### Event: 'error' |
| 947 | +### Event: `'error'` |
948 | 948 |
|
949 | 949 | * `err` {Error} The error. |
950 | 950 |
|
@@ -960,7 +960,7 @@ against accidentally invoking handler functions multiple times. |
960 | 960 |
|
961 | 961 | See also [`subprocess.kill()`][] and [`subprocess.send()`][]. |
962 | 962 |
|
963 | | -### Event: 'exit' |
| 963 | +### Event: `'exit'` |
964 | 964 | <!-- YAML |
965 | 965 | added: v0.1.90 |
966 | 966 | --> |
@@ -983,7 +983,7 @@ re-raise the handled signal. |
983 | 983 |
|
984 | 984 | See waitpid(2). |
985 | 985 |
|
986 | | -### Event: 'message' |
| 986 | +### Event: `'message'` |
987 | 987 | <!-- YAML |
988 | 988 | added: v0.5.9 |
989 | 989 | --> |
@@ -998,7 +998,7 @@ The `'message'` event is triggered when a child process uses |
998 | 998 | The message goes through serialization and parsing. The resulting |
999 | 999 | message might not be the same as what is originally sent. |
1000 | 1000 |
|
1001 | | -### subprocess.channel |
| 1001 | +### `subprocess.channel` |
1002 | 1002 | <!-- YAML |
1003 | 1003 | added: v7.1.0 |
1004 | 1004 | --> |
@@ -1008,7 +1008,7 @@ added: v7.1.0 |
1008 | 1008 | The `subprocess.channel` property is a reference to the child's IPC channel. If |
1009 | 1009 | no IPC channel currently exists, this property is `undefined`. |
1010 | 1010 |
|
1011 | | -### subprocess.connected |
| 1011 | +### `subprocess.connected` |
1012 | 1012 | <!-- YAML |
1013 | 1013 | added: v0.7.2 |
1014 | 1014 | --> |
@@ -1019,7 +1019,7 @@ The `subprocess.connected` property indicates whether it is still possible to |
1019 | 1019 | send and receive messages from a child process. When `subprocess.connected` is |
1020 | 1020 | `false`, it is no longer possible to send or receive messages. |
1021 | 1021 |
|
1022 | | -### subprocess.disconnect() |
| 1022 | +### `subprocess.disconnect()` |
1023 | 1023 | <!-- YAML |
1024 | 1024 | added: v0.7.2 |
1025 | 1025 | --> |
@@ -1038,7 +1038,7 @@ When the child process is a Node.js instance (e.g. spawned using |
1038 | 1038 | [`child_process.fork()`][]), the `process.disconnect()` method can be invoked |
1039 | 1039 | within the child process to close the IPC channel as well. |
1040 | 1040 |
|
1041 | | -### subprocess.kill(\[signal\]) |
| 1041 | +### `subprocess.kill([signal])` |
1042 | 1042 | <!-- YAML |
1043 | 1043 | added: v0.1.90 |
1044 | 1044 | --> |
@@ -1100,7 +1100,7 @@ setTimeout(() => { |
1100 | 1100 | }, 2000); |
1101 | 1101 | ``` |
1102 | 1102 |
|
1103 | | -### subprocess.killed |
| 1103 | +### `subprocess.killed` |
1104 | 1104 | <!-- YAML |
1105 | 1105 | added: v0.5.10 |
1106 | 1106 | --> |
@@ -1112,7 +1112,7 @@ The `subprocess.killed` property indicates whether the child process |
1112 | 1112 | successfully received a signal from `subprocess.kill()`. The `killed` property |
1113 | 1113 | does not indicate that the child process has been terminated. |
1114 | 1114 |
|
1115 | | -### subprocess.pid |
| 1115 | +### `subprocess.pid` |
1116 | 1116 | <!-- YAML |
1117 | 1117 | added: v0.1.90 |
1118 | 1118 | --> |
@@ -1129,7 +1129,7 @@ console.log(`Spawned child pid: ${grep.pid}`); |
1129 | 1129 | grep.stdin.end(); |
1130 | 1130 | ``` |
1131 | 1131 |
|
1132 | | -### subprocess.ref() |
| 1132 | +### `subprocess.ref()` |
1133 | 1133 | <!-- YAML |
1134 | 1134 | added: v0.7.10 |
1135 | 1135 | --> |
@@ -1150,7 +1150,7 @@ subprocess.unref(); |
1150 | 1150 | subprocess.ref(); |
1151 | 1151 | ``` |
1152 | 1152 |
|
1153 | | -### subprocess.send(message\[, sendHandle\[, options\]\]\[, callback\]) |
| 1153 | +### `subprocess.send(message[, sendHandle[, options]][, callback])` |
1154 | 1154 | <!-- YAML |
1155 | 1155 | added: v0.5.9 |
1156 | 1156 | changes: |
@@ -1331,7 +1331,7 @@ It is also recommended that any `'message'` handlers in the child process |
1331 | 1331 | verify that `socket` exists, as the connection may have been closed during the |
1332 | 1332 | time it takes to send the connection to the child. |
1333 | 1333 |
|
1334 | | -### subprocess.stderr |
| 1334 | +### `subprocess.stderr` |
1335 | 1335 | <!-- YAML |
1336 | 1336 | added: v0.1.90 |
1337 | 1337 | --> |
@@ -1346,7 +1346,7 @@ then this will be `null`. |
1346 | 1346 | `subprocess.stderr` is an alias for `subprocess.stdio[2]`. Both properties will |
1347 | 1347 | refer to the same value. |
1348 | 1348 |
|
1349 | | -### subprocess.stdin |
| 1349 | +### `subprocess.stdin` |
1350 | 1350 | <!-- YAML |
1351 | 1351 | added: v0.1.90 |
1352 | 1352 | --> |
@@ -1364,7 +1364,7 @@ then this will be `null`. |
1364 | 1364 | `subprocess.stdin` is an alias for `subprocess.stdio[0]`. Both properties will |
1365 | 1365 | refer to the same value. |
1366 | 1366 |
|
1367 | | -### subprocess.stdio |
| 1367 | +### `subprocess.stdio` |
1368 | 1368 | <!-- YAML |
1369 | 1369 | added: v0.7.10 |
1370 | 1370 | --> |
@@ -1404,7 +1404,7 @@ assert.strictEqual(subprocess.stdio[2], null); |
1404 | 1404 | assert.strictEqual(subprocess.stdio[2], subprocess.stderr); |
1405 | 1405 | ``` |
1406 | 1406 |
|
1407 | | -### subprocess.stdout |
| 1407 | +### `subprocess.stdout` |
1408 | 1408 | <!-- YAML |
1409 | 1409 | added: v0.1.90 |
1410 | 1410 | --> |
@@ -1429,7 +1429,7 @@ subprocess.stdout.on('data', (data) => { |
1429 | 1429 | }); |
1430 | 1430 | ``` |
1431 | 1431 |
|
1432 | | -### subprocess.unref() |
| 1432 | +### `subprocess.unref()` |
1433 | 1433 | <!-- YAML |
1434 | 1434 | added: v0.7.10 |
1435 | 1435 | --> |
|