From 05fbc80f45601e16f5e17dd28666d3d4e64aef0c Mon Sep 17 00:00:00 2001
From: Harshitha KP <harshi46@in.ibm.com>
Date: Thu, 16 Jan 2020 07:25:22 -0500
Subject: [PATCH] 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>
---
 doc/api/worker_threads.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/api/worker_threads.md b/doc/api/worker_threads.md
index d2989a2eeb6538..e867e161a89987 100644
--- a/doc/api/worker_threads.md
+++ b/doc/api/worker_threads.md
@@ -53,6 +53,10 @@ When implementing a worker pool, use the [`AsyncResource`][] API to inform
 diagnostic tools (e.g. in order to provide asynchronous stack traces) about the
 correlation between tasks and their outcomes.
 
+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
@@ -748,6 +752,7 @@ active handle in the event system. If the worker is already `unref()`ed calling
 [`require('worker_threads').workerData`]: #worker_threads_worker_workerdata
 [`trace_events`]: tracing.html
 [`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