Node.js comes with a variety of CLI options. These options expose built-in\ndebugging, multiple ways to execute scripts, and other helpful runtime options.
\nTo view this documentation as a manual page in a terminal, run man node.
node [options] [V8 options] [script.js | -e "script" | -] [--] [arguments]
node debug [script.js | -e "script" | <host>:<port>] …
node --v8-options
Execute without arguments to start the REPL.
\nFor more info about node debug, please see the debugger documentation.
Print node's version.
\n", "type": "module", "displayName": "`-v`, `--version`" }, { "textRaw": "`-h`, `--help`", "name": "`-h`,_`--help`", "meta": { "added": [ "v0.1.3" ], "changes": [] }, "desc": "Print node command line options.\nThe output of this option is less detailed than this document.
\n", "type": "module", "displayName": "`-h`, `--help`" }, { "textRaw": "`-e`, `--eval \"script\"`", "name": "`-e`,_`--eval_\"script\"`", "meta": { "added": [ "v0.5.2" ], "changes": [ { "version": "v5.11.0", "pr-url": "https://github.com/nodejs/node/pull/5348", "description": "Built-in libraries are now available as predefined variables." } ] }, "desc": "Evaluate the following argument as JavaScript. The modules which are\npredefined in the REPL can also be used in script.
On Windows, using cmd.exe a single quote will not work correctly because it\nonly recognizes double " for quoting. In Powershell or Git bash, both '\nand " are usable.
Identical to -e but prints the result.
Syntax check the script without executing.
\n", "type": "module", "displayName": "`-c`, `--check`" }, { "textRaw": "`-i`, `--interactive`", "name": "`-i`,_`--interactive`", "meta": { "added": [ "v0.7.7" ], "changes": [] }, "desc": "Opens the REPL even if stdin does not appear to be a terminal.
\n", "type": "module", "displayName": "`-i`, `--interactive`" }, { "textRaw": "`-r`, `--require module`", "name": "`-r`,_`--require_module`", "meta": { "added": [ "v1.6.0" ], "changes": [] }, "desc": "Preload the specified module at startup.
\nFollows require()'s module resolution\nrules. module may be either a path to a file, or a node module name.
Activate inspector on host:port. Default is 127.0.0.1:9229.
\nV8 inspector integration allows tools such as Chrome DevTools and IDEs to debug\nand profile Node.js instances. The tools attach to Node.js instances via a\ntcp port and communicate using the Chrome Debugging Protocol.
\n", "type": "module", "displayName": "`--inspect[=[host:]port]`" }, { "textRaw": "`--inspect-brk[=[host:]port]`", "name": "`--inspect-brk[=[host:]port]`", "meta": { "added": [ "v7.6.0" ], "changes": [] }, "desc": "Activate inspector on host:port and break at start of user script.\nDefault host:port is 127.0.0.1:9229.
\n", "type": "module", "displayName": "`--inspect-brk[=[host:]port]`" }, { "textRaw": "`--inspect-port=[host:]port`", "name": "`--inspect-port=[host:]port`", "meta": { "added": [ "v7.6.0" ], "changes": [] }, "desc": "Set the host:port to be used when the inspector is activated.\nUseful when activating the inspector by sending the SIGUSR1 signal.
Default host is 127.0.0.1.
\n", "type": "module", "displayName": "`--inspect-port=[host:]port`" }, { "textRaw": "`--no-deprecation`", "name": "`--no-deprecation`", "meta": { "added": [ "v0.8.0" ], "changes": [] }, "desc": "Silence deprecation warnings.
\n", "type": "module", "displayName": "`--no-deprecation`" }, { "textRaw": "`--trace-deprecation`", "name": "`--trace-deprecation`", "meta": { "added": [ "v0.8.0" ], "changes": [] }, "desc": "Print stack traces for deprecations.
\n", "type": "module", "displayName": "`--trace-deprecation`" }, { "textRaw": "`--throw-deprecation`", "name": "`--throw-deprecation`", "meta": { "added": [ "v0.11.14" ], "changes": [] }, "desc": "Throw errors for deprecations.
\n", "type": "module", "displayName": "`--throw-deprecation`" }, { "textRaw": "`--pending-deprecation`", "name": "`--pending-deprecation`", "meta": { "added": [ "v8.0.0" ], "changes": [] }, "desc": "Emit pending deprecation warnings.
\nPending deprecations are generally identical to a runtime deprecation with the\nnotable exception that they are turned off by default and will not be emitted\nunless either the --pending-deprecation command line flag, or the\nNODE_PENDING_DEPRECATION=1 environment variable, is set. Pending deprecations\nare used to provide a kind of selective "early warning" mechanism that\ndevelopers may leverage to detect deprecated API usage.
Silence all process warnings (including deprecations).
\n", "type": "module", "displayName": "`--no-warnings`" }, { "textRaw": "`--abort-on-uncaught-exception`", "name": "`--abort-on-uncaught-exception`", "meta": { "added": [ "v0.10" ], "changes": [] }, "desc": "Aborting instead of exiting causes a core file to be generated for post-mortem\nanalysis using a debugger (such as lldb, gdb, and mdb).
If this flag is passed, the behavior can still be set to not abort through\nprocess.setUncaughtExceptionCaptureCallback() (and through usage of the\ndomain module that uses it).
Print stack traces for process warnings (including deprecations).
\n", "type": "module", "displayName": "`--trace-warnings`" }, { "textRaw": "`--redirect-warnings=file`", "name": "`--redirect-warnings=file`", "meta": { "added": [ "v8.0.0" ], "changes": [] }, "desc": "Write process warnings to the given file instead of printing to stderr. The\nfile will be created if it does not exist, and will be appended to if it does.\nIf an error occurs while attempting to write the warning to the file, the\nwarning will be written to stderr instead.
\n", "type": "module", "displayName": "`--redirect-warnings=file`" }, { "textRaw": "`--trace-sync-io`", "name": "`--trace-sync-io`", "meta": { "added": [ "v2.1.0" ], "changes": [] }, "desc": "Prints a stack trace whenever synchronous I/O is detected after the first turn\nof the event loop.
\n", "type": "module", "displayName": "`--trace-sync-io`" }, { "textRaw": "`--no-force-async-hooks-checks`", "name": "`--no-force-async-hooks-checks`", "meta": { "added": [ "v9.0.0" ], "changes": [] }, "desc": "Disables runtime checks for async_hooks. These will still be enabled\ndynamically when async_hooks is enabled.
Enables the collection of trace event tracing information.
\n", "type": "module", "displayName": "`--trace-events-enabled`" }, { "textRaw": "`--trace-event-categories`", "name": "`--trace-event-categories`", "meta": { "added": [ "v7.7.0" ], "changes": [] }, "desc": "A comma separated list of categories that should be traced when trace event\ntracing is enabled using --trace-events-enabled.
Template string specifying the filepath for the trace event data, it\nsupports ${rotation} and ${pid}.
Automatically zero-fills all newly allocated Buffer and SlowBuffer\ninstances.
\n", "type": "module", "displayName": "`--zero-fill-buffers`" }, { "textRaw": "`--preserve-symlinks`", "name": "`--preserve-symlinks`", "meta": { "added": [ "v6.3.0" ], "changes": [] }, "desc": "Instructs the module loader to preserve symbolic links when resolving and\ncaching modules.
\nBy default, when Node.js loads a module from a path that is symbolically linked\nto a different on-disk location, Node.js will dereference the link and use the\nactual on-disk "real path" of the module as both an identifier and as a root\npath to locate other dependency modules. In most cases, this default behavior\nis acceptable. However, when using symbolically linked peer dependencies, as\nillustrated in the example below, the default behavior causes an exception to\nbe thrown if moduleA attempts to require moduleB as a peer dependency:
{appDir}\n ├── app\n │ ├── index.js\n │ └── node_modules\n │ ├── moduleA -> {appDir}/moduleA\n │ └── moduleB\n │ ├── index.js\n │ └── package.json\n └── moduleA\n ├── index.js\n └── package.json\nThe --preserve-symlinks command line flag instructs Node.js to use the\nsymlink path for modules as opposed to the real path, allowing symbolically\nlinked peer dependencies to be found.
Note, however, that using --preserve-symlinks can have other side effects.\nSpecifically, symbolically linked native modules can fail to load if those\nare linked from more than one location in the dependency tree (Node.js would\nsee those as two separate modules and would attempt to load the module multiple\ntimes, causing an exception to be thrown).
Track heap object allocations for heap snapshots.
\n", "type": "module", "displayName": "`--track-heap-objects`" }, { "textRaw": "`--prof-process`", "name": "`--prof-process`", "meta": { "added": [ "v5.2.0" ], "changes": [] }, "desc": "Process V8 profiler output generated using the V8 option --prof.
Print V8 command line options.
\nV8 options allow words to be separated by both dashes (-) or\nunderscores (_).
For example, --stack-trace-limit is equivalent to --stack_trace_limit.
Specify an alternative default TLS cipher list. (Requires Node.js to be built\nwith crypto support. (Default))
\n", "type": "module", "displayName": "`--tls-cipher-list=list`" }, { "textRaw": "`--enable-fips`", "name": "`--enable-fips`", "meta": { "added": [ "v6.0.0" ], "changes": [] }, "desc": "Enable FIPS-compliant crypto at startup. (Requires Node.js to be built with\n./configure --openssl-fips)
Force FIPS-compliant crypto on startup. (Cannot be disabled from script code.)\n(Same requirements as --enable-fips)
Load an OpenSSL configuration file on startup. Among other uses, this can be\nused to enable FIPS-compliant crypto if Node.js is built with\n./configure --openssl-fips.
Use OpenSSL's default CA store or use bundled Mozilla CA store as supplied by\ncurrent Node.js version. The default store is selectable at build-time.
\nUsing OpenSSL store allows for external modifications of the store. For most\nLinux and BSD distributions, this store is maintained by the distribution\nmaintainers and system administrators. OpenSSL CA store location is dependent on\nconfiguration of the OpenSSL library but this can be altered at runtime using\nenvironment variables.
\nThe bundled CA store, as supplied by Node.js, is a snapshot of Mozilla CA store\nthat is fixed at release time. It is identical on all supported platforms.
\nSee SSL_CERT_DIR and SSL_CERT_FILE.
Specify ICU data load path. (overrides NODE_ICU_DATA)
Alias for stdin, analogous to the use of - in other command line utilities,\nmeaning that the script will be read from stdin, and the rest of the options\nare passed to that script.
\n", "type": "module", "displayName": "`-`" }, { "textRaw": "`--`", "name": "`--`", "meta": { "added": [ "v6.11.0" ], "changes": [] }, "desc": "Indicate the end of node options. Pass the rest of the arguments to the script.\nIf no script filename or eval/print script is supplied prior to this, then\nthe next argument will be used as a script filename.
\n", "type": "module", "displayName": "`--`" } ], "type": "misc", "displayName": "Options" }, { "textRaw": "Environment Variables", "name": "environment_variables", "modules": [ { "textRaw": "`NODE_DEBUG=module[,…]`", "name": "`node_debug=module[,…]`", "meta": { "added": [ "v0.1.32" ], "changes": [] }, "desc": "','-separated list of core modules that should print debug information.
':'-separated list of directories prefixed to the module search path.
On Windows, this is a ';'-separated list instead.
When set to 1 colors will not be used in the REPL.
Data path for ICU (Intl object) data. Will extend linked-in data when compiled\nwith small-icu support.
\n", "type": "module", "displayName": "`NODE_ICU_DATA=file`" }, { "textRaw": "`NODE_NO_WARNINGS=1`", "name": "`node_no_warnings=1`", "meta": { "added": [ "v6.11.0" ], "changes": [] }, "desc": "When set to 1, process warnings are silenced.
A space-separated list of command line options. options... are interpreted as\nif they had been specified on the command line before the actual command line\n(so they can be overridden). Node will exit with an error if an option that is\nnot allowed in the environment is used, such as -p or a script file.
Node options that are allowed are:
\n--enable-fips--force-fips--icu-data-dir--inspect-brk--inspect-port--inspect--no-deprecation--no-warnings--openssl-config--redirect-warnings--require, -r--throw-deprecation--tls-cipher-list--trace-deprecation--trace-events-categories--trace-events-enabled--trace-event-file-pattern--trace-sync-io--trace-warnings--track-heap-objects--use-bundled-ca--use-openssl-ca--v8-pool-size--zero-fill-buffersV8 options that are allowed are:
\n--abort-on-uncaught-exception--max-old-space-size--perf-basic-prof--perf-prof--stack-trace-limitWhen set to 1, emit pending deprecation warnings.
Pending deprecations are generally identical to a runtime deprecation with the\nnotable exception that they are turned off by default and will not be emitted\nunless either the --pending-deprecation command line flag, or the\nNODE_PENDING_DEPRECATION=1 environment variable, is set. Pending deprecations\nare used to provide a kind of selective "early warning" mechanism that\ndevelopers may leverage to detect deprecated API usage.
When set to 1, instructs the module loader to preserve symbolic links when\nresolving and caching modules.
Path to the file used to store the persistent REPL history. The default path is\n~/.node_repl_history, which is overridden by this variable. Setting the value\nto an empty string ("" or " ") disables persistent REPL history.
When set, the well known "root" CAs (like VeriSign) will be extended with the\nextra certificates in file. The file should consist of one or more trusted\ncertificates in PEM format. A message will be emitted (once) with\nprocess.emitWarning() if the file is missing or\nmalformed, but any errors are otherwise ignored.
Note that neither the well known nor extra certificates are used when the ca\noptions property is explicitly specified for a TLS or HTTPS client or server.
Load an OpenSSL configuration file on startup. Among other uses, this can be\nused to enable FIPS-compliant crypto if Node.js is built with ./configure\n--openssl-fips.
If the --openssl-config command line option is used, the environment\nvariable is ignored.
If --use-openssl-ca is enabled, this overrides and sets OpenSSL's directory\ncontaining trusted certificates.
Be aware that unless the child environment is explicitly set, this environment\nvariable will be inherited by any child processes, and if they use OpenSSL, it\nmay cause them to trust the same CAs as node.
\n", "type": "module", "displayName": "`SSL_CERT_DIR=dir`" }, { "textRaw": "`SSL_CERT_FILE=file`", "name": "`ssl_cert_file=file`", "meta": { "added": [ "v7.7.0" ], "changes": [] }, "desc": "If --use-openssl-ca is enabled, this overrides and sets OpenSSL's file\ncontaining trusted certificates.
Be aware that unless the child environment is explicitly set, this environment\nvariable will be inherited by any child processes, and if they use OpenSSL, it\nmay cause them to trust the same CAs as node.
\n", "type": "module", "displayName": "`SSL_CERT_FILE=file`" }, { "textRaw": "`NODE_REDIRECT_WARNINGS=file`", "name": "`node_redirect_warnings=file`", "meta": { "added": [ "v8.0.0" ], "changes": [] }, "desc": "When set, process warnings will be emitted to the given file instead of\nprinting to stderr. The file will be created if it does not exist, and will be\nappended to if it does. If an error occurs while attempting to write the\nwarning to the file, the warning will be written to stderr instead. This is\nequivalent to using the --redirect-warnings=file command-line flag.
Set the number of threads used in libuv's threadpool to size threads.
Asynchronous system APIs are used by Node.js whenever possible, but where they\ndo not exist, libuv's threadpool is used to create asynchronous node APIs based\non synchronous system APIs. Node.js APIs that use the threadpool are:
\nfs APIs, other than the file watcher APIs and those that are explicitly\nsynchronouscrypto.pbkdf2()crypto.randomBytes(), unless it is used without a callbackcrypto.randomFill()dns.lookup()zlib APIs, other than those that are explicitly synchronousBecause libuv's threadpool has a fixed size, it means that if for whatever\nreason any of these APIs takes a long time, other (seemingly unrelated) APIs\nthat run in libuv's threadpool will experience degraded performance. In order to\nmitigate this issue, one potential solution is to increase the size of libuv's\nthreadpool by setting the 'UV_THREADPOOL_SIZE' environment variable to a value\ngreater than 4 (its current default value). For more information, see the\nlibuv threadpool documentation.