doc: visibility of Worker threads cli options

Fixes: https://github.com/nodejs/node/issues/28518
PR-URL: https://github.com/nodejs/node/pull/31380
Fixes: https://github.com/nodejs/node/issues/28518
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
pull/32088/head
Harshitha KP 2020-01-16 07:25:22 -05:00 committed by Anna Henningsen
parent bf7409e974
commit 37287d3f58
No known key found for this signature in database
GPG Key ID: A94130F0BFC8EBE9
1 changed files with 5 additions and 0 deletions

View File

@ -55,6 +55,10 @@ correlation between tasks and their outcomes. See
["Using `AsyncResource` for a `Worker` thread pool"][async-resource-worker-pool]
in the `async_hooks` documentation for an example implementation.
Worker threads inherit non-process-specific options by default. Refer to
[`Worker constructor options`][] to know how to customize worker thread options,
specifically `argv` and `execArgv` options.
## `worker.isMainThread`
<!-- YAML
added: v10.5.0
@ -768,6 +772,7 @@ active handle in the event system. If the worker is already `unref()`ed calling
[`trace_events`]: tracing.html
[`v8.getHeapSnapshot()`]: v8.html#v8_v8_getheapsnapshot
[`vm`]: vm.html
[`Worker constructor options`]: #worker_threads_new_worker_filename_options
[`worker.on('message')`]: #worker_threads_event_message_1
[`worker.postMessage()`]: #worker_threads_worker_postmessage_value_transferlist
[`worker.SHARE_ENV`]: #worker_threads_worker_share_env