NODE22(1)

📦 version 22.23.4, in opensuse-leap 16.0

🦋 node22(1) 🦋

okay so this is the manual page for node22 — server-side JavaScript runtime — and bestie, it is long, so buckle up 🫶

🎀 NAME 🎀

node22 — server-side JavaScript runtime. that's the whole vibe. it runs JavaScript, but not in a browser, and it does it iconically 👑

✨ SYNOPSIS ✨

like, here's how you actually invoke it:

node22 [options] [v8-options] [-e string | script.js | -] [--]
       [arguments ...]
node22 inspect [-e string | script.js | - | <host>:<port>] ...
node22 [--v8-options]

three moods. pick your fighter 💅

💜 DESCRIPTION 💜

so Node.js is a set of libraries for JavaScript which allows it to be used outside of the browser. no window object, no problem. it's primarily focused on creating simple, easy-to-build network clients and servers — like that's literally its whole thing 🧚

and listen — execute node22 without any arguments and it just starts a REPL. yes, an interactive one. it's giving "just you and the prompt, bestie" ✨

🌈 OPTIONS 🌈

okay this is the big one. every single flag, no skipping, no cap 🔥

  • - — alias for stdin, analogous to the use of - in other command-line utilities. the executed script is read from stdin, and the remaining arguments are passed to the script.
  • -- — indicates the end of command-line options. everything after it gets passed to the script.

and if no script filename or eval/print script was supplied before this, then the next argument will be used as a script filename. iykyk 💅

  • --abort-on-uncaught-exception — aborting instead of exiting causes a core file to be generated for analysis. dramatic? yes. useful? also yes 🩺
  • --allow-fs-read — allow file system read access when using the permission model.
  • --allow-fs-write — allow file system write access when using the permission model.
  • --allow-addons — allow using native addons when using the permission model.
  • --allow-child-process — allow spawning process when using the permission model.
  • --allow-wasi — allow execution of WASI when using the permission model.
  • --allow-worker — allow creating worker threads when using the permission model.
  • --completion-bash — print a source-able bash completion script for Node.js. tab-complete slay 🐚
  • -C, --conditions string — use custom conditional exports conditions. string.
  • --cpu-prof — start the V8 CPU profiler on start up, and write the CPU profile to disk before exit. if --cpu-prof-dir is not specified, the profile will be written to the current working directory with a generated file name 📊
  • --cpu-prof-dir — the directory where the CPU profiles generated by --cpu-prof will be placed. the default value is controlled by the --diagnostic-dir command-line option.
  • --cpu-prof-interval — the sampling interval in microseconds for the CPU profiles generated by --cpu-prof. the default is 1000.
  • --cpu-prof-name — file name of the V8 CPU profile generated with --cpu-prof.
  • --diagnostic-dir — set the directory for all diagnostic output files. default is current working directory. set the directory to which all diagnostic output files will be written to. defaults to current working directory. affects the default output directory of: --cpu-prof-dir, --heap-prof-dir, --redirect-warnings. one folder to rule them all 🗂️
  • --disable-proto=mode — disable the Object.prototype.__proto__ property. if mode is delete, the property will be removed entirely. if mode is throw, accesses to the property will throw an exception with the code ERR_PROTO_ACCESS. choose your chaos 💀
  • --disable-wasm-trap-handler=mode — disable trap-handler-based WebAssembly bound checks and fall back to inline bound checks so that WebAssembly can be run with limited virtual memory.
  • --disallow-code-generation-from-strings — make built-in language features like eval and new Function that generate code from strings throw an exception instead. this does not affect the Node.js vm module. (read that again, bestie — vm is exempt 🙈)
  • --enable-fips — enable FIPS-compliant crypto at startup. requires Node.js to be built with ./configure --openssl-fips. no build flag, no FIPS, that's the rule 🔐
  • --enable-source-maps — enable Source Map V3 support for stack traces. your stack traces, but make them make sense ✨
  • --entry-url — interpret the entry point as a URL.
  • --experimental-addon-modules — enable experimental addon module support.
  • --experimental-default-type=type — interpret as either ES modules or CommonJS modules input via --eval or STDIN, when --input-type is unspecified;
  • --experimental-config-file — specifies the configuration file to load.
  • --experimental-default-config-file — enable support for automatically loading node.config.json.
  • --experimental-import-meta-resolve — enable experimental ES modules support for import.meta.resolve().
  • --experimental-loader=module — specify the module to use as a custom module loader.
  • --permission — enable the permission model. (yes it lives down here alphabetically, don't @ me)
  • --experimental-shadow-realm — use this flag to enable ShadowRealm support.
  • --experimental-test-coverage — enable code coverage in the test runner.
  • --experimental-test-isolation=mode — configures the type of test isolation used in the test runner.
  • --experimental-test-module-mocks — enable module mocking in the test runner.
  • --experimental-transform-types — enable transformation of TypeScript-only syntax into JavaScript code.
  • --experimental-eventsource — enable experimental support for the EventSource Web API.
  • --no-experimental-fetch — disable experimental support for the Fetch API.
  • --no-experimental-websocket — disable experimental support for the WebSocket API.
  • --experimental-webstorage — enable experimental support for the Web Storage API.
  • --no-experimental-global-customevent — disable exposition of the CustomEvent on the global scope.
  • --no-experimental-global-webcrypto — disable exposition of the Web Crypto API on the global scope.
  • --no-experimental-repl-await — disable top-level await keyword support in REPL.
  • --no-experimental-sqlite — disable the experimental node:sqlite module.
  • --no-experimental-strip-types — disable experimental type-stripping for TypeScript files.
  • --experimental-vm-modules — enable experimental ES module support in VM module.
  • --experimental-wasi-unstable-preview1 — enable experimental WebAssembly System Interface support. this flag is no longer required as WASI is enabled by default 🦋
  • --experimental-inspector-network-resource — enable experimental support for inspector network resources.
  • --force-context-aware — disable loading native addons that are not context-aware.
  • --force-fips — force FIPS-compliant crypto on startup (cannot be disabled from script code). same requirements as --enable-fips. once it's on, it's on 🔒
  • --frozen-intrinsics — enable experimental frozen intrinsics support.
  • --heapsnapshot-near-heap-limit=max_count — generate heap snapshot when the V8 heap usage is approaching the heap limit. no more than the specified number of snapshots will be generated.
  • --heapsnapshot-signal=signal — generate heap snapshot on specified signal.
  • --heap-prof — start the V8 heap profiler on start up, and write the heap profile to disk before exit. if --heap-prof-dir is not specified, the profile will be written to the current working directory with a generated file name 🧠
  • --heap-prof-dir — the directory where the heap profiles generated by --heap-prof will be placed. the default value is controlled by the --diagnostic-dir command-line option.
  • --heap-prof-interval — the average sampling interval in bytes for the heap profiles generated by --heap-prof. the default is 512 * 1024.
  • --heap-prof-name — file name of the V8 heap profile generated with --heap-prof.
  • --icu-data-dir=file — specify ICU data load path. overrides NODE_ICU_DATA.
  • --input-type=type — set the module resolution type for input via --eval, --print or STDIN.
  • --inspect-brk=[host:]port — activate inspector on host:port and break at start of user script. breakpoint immediately, main character energy 🎬
  • --inspect-port=[host:]port — set the host:port to be used when the inspector is activated.
  • --inspect-publish-uid=stderr,http — specify how the inspector WebSocket URL is exposed. valid values are stderr and http. default is stderr,http.
  • --inspect-wait=[host:]port — activate inspector on host:port and wait for debugger to be attached.
  • --inspect=[host:]port — activate inspector on host:port. default is 127.0.0.1:9229.

V8 Inspector integration allows attaching Chrome DevTools and IDEs to Node.js instances for debugging and profiling. it uses the Chrome DevTools Protocol. literally the dream collab 🤝

  • --insecure-http-parser — use an insecure HTTP parser that accepts invalid HTTP headers. this may allow interoperability with non-conformant HTTP implementations. it may also allow request smuggling and other HTTP attacks that rely on invalid headers being accepted. avoid using this option.
🚨 bestie no. i'm serious. avoid using this option. it's right there in the manual. smuggling attacks are not the vibe 💀
  • --jitless — disable runtime allocation of executable memory. this may be required on some platforms for security reasons. it can also reduce attack surface on other platforms, but the performance impact may be severe.

this flag is inherited from V8 and is subject to change upstream. it may disappear in a non-semver-major release. so don't get too attached 👀

  • --localstorage-file=file — the file used to store localStorage data.
  • --max-http-header-size=size — specify the maximum size of HTTP headers in bytes. defaults to 16 KiB.
  • --max-old-space-size-percentage=percentage — sets the maximum memory size of V8's old memory section as a percentage of available system memory. this flag takes precedence over --max-old-space-size when both are specified. the percentage parameter must be a number greater than 0 and up to 100, representing the percentage of available system memory to allocate to the V8 heap.
note: this flag utilizes --max-old-space-size, which may be unreliable on 32-bit platforms due to integer overflow issues. so… 32-bit besties, beware 😭
  • --napi-modules — this option is a no-op. it is kept for compatibility. it does literally nothing and it's staying. respect the legacy 💅
  • --no-deprecation — silence deprecation warnings. (ignorance is bliss, apparently)
  • --no-extra-info-on-fatal-exception — hide extra information on fatal exception that causes exit.
  • --no-force-async-hooks-checks — disable runtime checks for async_hooks. these will still be enabled dynamically when async_hooks is enabled.
  • --no-addons — disable the node-addons exports condition as well as disable loading native addons. when --no-addons is specified, calling process.dlopen or requiring a native C++ addon will fail and throw an exception. so like, don't try it 🫠

Okay bestie, buckle up, the flag wall continues 💅 no skipping, we read all of these.

  • --no-global-search-paths — literally just don't search for modules in global paths. that's it, that's the whole vibe 🚫
  • --no-warnings — silences all process warnings, and yes that includes deprecations. quiet mode activated 🤫
  • --node-memory-debug — turns on extra debug checks for memory leaks inside Node.js internals. honestly this is only useful if you're debugging Node.js itself, like the actual runtime. not your app. respect tho 🫡
  • --openssl-config=file — loads an OpenSSL configuration file at startup. among other uses, you can use this to enable FIPS-compliant crypto if Node.js was built with ./configure --openssl-fips. fancy 🔐
  • --pending-deprecation — emits pending deprecation warnings. the ones that aren't yelling yet, they're just... foreshadowing 💀
  • --preserve-symlinks — tells the module loader to preserve symbolic links when resolving and caching modules. heads up: this is for modules other than the main module 👀
  • --preserve-symlinks-main — same symlink-preserving energy, but specifically for the main module. main character treatment, obviously 👑
  • --prof — generates V8 profiler output. numbers! graphs! performance lore! 📈
  • --prof-process — processes the V8 profiler output that was generated using the V8 option --prof. the follow-up step, iykyk 🔁
  • --redirect-warnings=file — writes process warnings into the given file instead of printing them to stderr. redirect that negativity 🎀
  • --report-compact — writes diagnostic reports in a compact format: single-line JSON. minimal, clean, slay ✨
  • --report-dir, --report-directory — the location where the diagnostic report gets generated. the file name may be an absolute path. if it's not absolute, then the default directory it gets written to is controlled by the --diagnostic-dir command-line option. path girlies rise 🗂️
  • --report-filename — the name of the file the diagnostic report gets written to. name your child 📝
  • --report-on-fatalerror — makes the diagnostic report trigger on fatal errors — and by that we mean internal errors inside the Node.js runtime, like running out of memory — that lead to your application terminating. super useful for inspecting diagnostic data elements like heap, stack, event loop state, resource consumption etc. so you can actually reason about the fatal error. detective mode 🔍
  • --report-on-signal — makes a diagnostic report get generated when the running Node.js process receives the specified (or predefined) signal. the default signal is SIGUSR2 📡
  • --report-signal — sets or resets the signal used for diagnostic report generation. not supported on Windows. default signal is SIGUSR2 🪟🚫
  • --report-uncaught-exception — generates a diagnostic report on un-caught exceptions. great for inspecting your JavaScript stack alongside the native stack and other runtime environment data. the receipts 🧾
  • --secure-heap=n — sets the size of the OpenSSL secure heap. any value less than 2 disables the secure heap. default is 0. the value must be a power of two. rules are rules 🌸
  • --secure-heap-min=n — sets the minimum allocation from the OpenSSL secure heap. default is 2, and again the value must be a power of two. two-pilled 🧚
  • --test — starts the Node.js command line test runner. test era begins 🧪
  • --test-concurrency — the maximum number of test files that the test runner CLI will execute concurrently. how many at once, bestie 🏃‍♀️
  • --test-coverage-branches=threshold — requires a minimum threshold for branch coverage (0 - 100) 🌿
  • --test-coverage-exclude — a glob pattern that excludes matching files from the coverage report. not you, girl 🙅‍♀️
  • --test-coverage-functions=threshold — requires a minimum threshold for function coverage (0 - 100) 🧮
  • --test-coverage-include — a glob pattern that only includes matching files in the coverage report. this is the VIP list 🎟️
  • --test-coverage-lines=threshold — requires a minimum threshold for line coverage (0 - 100) 📏
  • --test-force-exit — configures the test runner to exit the process once all known tests have finished executing, even if the event loop would otherwise remain active. bye, we're done here 👋
  • --test-name-pattern — a regular expression that configures the test runner to only execute tests whose name matches the pattern you gave it. regex girlies, this one's for you 💜
  • --test-reporter — a test reporter to use when running tests. pick your narrator 🎙️
  • --test-reporter-destination — the destination for the corresponding test reporter. where the narration goes 📬
  • --test-only — configures the test runner to only execute top level tests that have the only option set. exclusive ✨
  • --test-shard — the test suite shard to execute, in a format of <index>/<total>. divide and conquer 🍰
  • --test-skip-pattern — a regular expression that configures the test runner to skip tests whose name matches the pattern. not invited 🚫
  • --test-timeout — a number of milliseconds after which the test execution will fail. the clock is ticking ⏰
  • --test-update-snapshots — regenerates the snapshot file used by the test runner for snapshot testing. refresh 🦋
  • --throw-deprecation — throws errors for deprecations. no more gentle warnings, we're throwing hands 😤
  • --title=title — specify process.title on startup. name your process 💖
  • --tls-cipher-list=list — specify an alternative default TLS cipher list. requires Node.js to be built with crypto support. (Default) 🔒
  • --tls-keylog=file — logs TLS key material to a file. the key material is in NSS SSLKEYLOGFILE format, and software (such as Wireshark) can use it to decrypt the TLS traffic. yes this is as spicy as it sounds 🕵️‍♀️
  • --tls-max-v1.2 — sets the default maxVersion to 'TLSv1.2'. use it to disable support for TLSv1.3 🔽
  • --tls-max-v1.3 — sets the default maxVersion to 'TLSv1.3'. use it to enable support for TLSv1.3 🔼
  • --tls-min-v1.0 — sets the default minVersion to 'TLSv1'. use for compatibility with old TLS clients or servers 🧓
  • --tls-min-v1.1 — sets the default minVersion to 'TLSv1.1'. use for compatibility with old TLS clients or servers 🧓
  • --tls-min-v1.2 — sets the default minVersion to 'TLSv1.2'. this is the default for 12.x and later, but the option is supported for compatibility with older Node.js versions 🫶
  • --tls-min-v1.3 — sets the default minVersion to 'TLSv1.3'. use it to disable support for TLSv1.2 in favour of TLSv1.3, which is more secure 🔐
  • --trace-atomics-wait — prints short summaries of calls to Atomics.wait(). this flag is deprecated ⚠️
  • --trace-deprecation — prints stack traces for deprecations. show me the receipts 🧾
  • --trace-event-categories categories — a comma-separated list of categories that should be traced when trace event tracing is enabled using --trace-events-enabled 🏷️
  • --trace-event-file-pattern pattern — a template string specifying the filepath for the trace event data. it supports ${rotation} and ${pid} 🌀
  • --trace-events-enabled — enables the collection of trace event tracing information. collect the lore 📚
  • --trace-exit — prints a stack trace whenever an environment is exited proactively, i.e. invoking process.exit() 🚪
  • --trace-sigint — prints a stack trace on SIGINT 🛑
  • --trace-sync-io — prints a stack trace whenever synchronous I/O is detected after the first turn of the event loop. caught in 4k 😭
  • --trace-tls — prints TLS packet trace information to stderr 📨
  • --trace-uncaught — prints stack traces for uncaught exceptions. usually the stack trace associated with the creation of an Error is printed, whereas this makes Node.js also print the stack trace associated with throwing the value (which does not need to be an Error instance). warning: enabling this option may affect garbage collection behavior negatively 💀
  • --trace-warnings — prints stack traces for process warnings (including deprecations) 🪵
  • --track-heap-objects — tracks heap object allocations for heap snapshots. keeping tabs 👀
  • --unhandled-rejections=mode — defines the behavior for unhandled rejections. mode can be one of strict (raise an error), warn (enforce warnings) or none (silence warnings) 🎚️
  • --use-bundled-ca, --use-openssl-ca — use the bundled Mozilla CA store as supplied by your current Node.js version, or use OpenSSL's default CA store. the default store is selectable at build-time 🏗️

okay so about the bundled CA store: as supplied by Node.js, it's a snapshot of the Mozilla CA store that's fixed at release time. it's identical on all supported platforms 🌍

using the OpenSSL store allows for external modifications of the store. for most Linux and BSD distributions, this store is maintained by the distribution maintainers and system administrators. the OpenSSL CA store location depends on the configuration of the OpenSSL library, but you can alter this at runtime using environment variables 🔧

see SSL_CERT_DIR and SSL_CERT_FILE 📂

  • --use-env-proxy — parses proxy settings from the HTTP_PROXY/HTTPS_PROXY/NO_PROXY environment variables and applies the setting in global HTTP/HTTPS clients 🌐
  • --use-system-ca — uses the trusted CA certificates present in the system store, in addition to the certificates in the bundled Mozilla CA store and certificates from NODE_EXTRA_CA_CERTS. on Windows and macOS, it uses system APIs to integrate additional trusted certificates. on other platforms it's similar to --use-openssl-ca, except that it caches the certificates on first load, and the system certificates are added in a complementary manner without replacing certificates from other sources. this flag supersedes --use-openssl-ca 👑
  • --use-largepages=mode — re-maps the Node.js static code to large memory pages at startup. if the target system supports it, this moves the Node.js static code onto 2 MiB pages instead of 4 KiB pages 🐘

mode must be one of these values: off (the default value, meaning do not map), on (map and ignore failure, reporting it to stderr), or silent (map and silently ignore failure) 🤐

  • --v8-options — prints V8 command-line options ⚙️
  • --v8-pool-size=num — sets V8's thread pool size, which is used to allocate background jobs. if it's set to 0, then V8 will choose an appropriate thread pool size based on the number of online processors. if the value you provide is larger than V8's maximum, then the largest value will be chosen. math 🧠
  • --watch — starts Node.js in watch mode. when it's in watch mode, changes in the watched files cause the Node.js process to restart. live, laugh, reload 🔄

Like, by default watch mode is gonna watch the entry point plus any required or imported module. Want more control? Use --watch-path to specify what paths to watch. 💅

  • --watch-path — Starts Node.js in watch mode and tells it exactly what paths to watch. When you're in watch mode, changes in the watched paths make the Node.js process restart. Heads up though: this turns off watching of required or imported modules, even when you use it together with --watch. So like, pick your fighter. 🫶
  • --watch-kill-signal — Customizes the signal that gets sent to the process on watch mode restarts. You're the one choosing the vibe of the goodbye. ✨
  • --zero-fill-buffers — Automatically zero-fills every newly allocated Buffer and SlowBuffer instance. Clean slate energy, literally. 🧚
  • -c, --check — Checks the script's syntax without executing it. Exits with an error code if the script is invalid. It's giving "read it before you send it" bestie. 😭
  • -e, --eval string — Evaluate string as JavaScript. Just, like, straight into it.
  • -h, --help — Print command-line options. Ngl the output of this option is less detailed than this document, so if you want the full tea, keep reading. 🎀
  • -i, --interactive — Opens the REPL even if stdin does not appear to be a terminal. Main character behavior: forcing the interaction. 💅
  • -p, --print string — Identical to -e, but prints the result. So you actually get to see it. Obsessed.
  • -r, --require module — Preloads the specified module at startup. Follows require()'s module resolution rules. module can be either a path to a file, or a Node.js module name. Either way it's coming with you. 🌸
  • -v, --version — Print node's version. The classic "who even am I right now" check. 🦋

🌈 ENVIRONMENT 🌈

The environment variables are literally the backstage pass, bestie. This is where the real customization lives.

  • FORCE_COLOR — Used to enable ANSI colorized output. The value may be one of: 1, true, or an empty string, to indicate 16-color support; 2 to indicate 256-color support; or 3 to indicate 16 million-color support. When used and set to a supported value, both the NO_COLOR and NODE_DISABLE_COLORS environment variables are ignored. Any other value will result in colorized output being disabled. So like, be precise, okay? 🌈
  • NO_COLOR — Alias for NODE_DISABLE_COLORS. Same energy, shorter name.
  • NODE_COMPILE_CACHE dir — Enable the module compile cache for the Node.js instance. Speed things up, slay. ⭐
  • NODE_DEBUG modules... — Comma-separated list of core modules that should print debug information. Turn on the little spy cameras. 👑
  • NODE_DEBUG_NATIVE modules... — Comma-separated list of C++ core modules that should print debug information. Same but for the C++ girlies.
  • NODE_DISABLE_COMPILE_CACHE — Disable the module compile cache for the Node.js instance. Sometimes you just gotta turn it off, no cap.
  • NODE_DISABLE_COLORS — When set to 1, colors will not be used in the REPL. Monochrome moment. 🖤
  • NODE_EXTRA_CA_CERTS file — When set, the well-known "root" CAs (like VeriSign) will be extended with the extra certificates in file. The file should consist of one or more trusted certificates in PEM format. If file is missing or misformatted, a message will be emitted once using process.emitWarning(), but any errors are otherwise ignored. This environment variable is ignored when node runs as setuid root or has Linux file capabilities set. Also, the NODE_EXTRA_CA_CERTS environment variable is only read when the Node.js process is first launched — changing the value at runtime using process.env.NODE_EXTRA_CA_CERTS has no effect on the current process. So like, commit at boot or don't bother. 🙈
  • NODE_ICU_DATA file — Data path for ICU (Intl object) data. Will extend linked-in data when compiled with small-icu support.
  • NODE_NO_WARNINGS — When set to 1, process warnings are silenced. Shhh. Peace and quiet. 🤫 (that's the vibe, anyway)
  • NODE_OPTIONS options... — A space-separated list of command-line options, which are interpreted as if they had been specified on the command line before the actual command (so they can be overridden). Node.js will exit with an error if an option that is not allowed in the environment is used, such as --print or a script file. So, like, not everything gets an invite to this party. 🎟️
  • NODE_PATH directories... — A colon-separated list of directories prefixed to the module search path. Point the loader in the right direction. 🧭
  • NODE_PENDING_DEPRECATION — When set to 1, emit pending deprecation warnings. Warning you before it's a whole problem. 💜
  • NODE_PENDING_PIPE_INSTANCES — Set the number of pending pipe instance handles when the pipe server is waiting for connections. This setting applies to Windows only. 🪟
  • NODE_PRESERVE_SYMLINKS — When set to 1, the module loader preserves symbolic links when resolving and caching modules. Keeping the shortcuts intact, fr fr.
  • NODE_REDIRECT_WARNINGS file — Write process warnings to the given file instead of printing to stderr. Equivalent to passing --redirect-warnings file on the command line. Diary entry but make it stderr. 🍓
  • NODE_REPL_HISTORY file — Path to the file used to store persistent REPL history. The default path is ~/.node_repl_history, which is overridden by this variable. Setting the value to an empty string ("" or " ") will disable persistent REPL history. Ghost mode: enabled. 👻
  • NODE_REPL_EXTERNAL_MODULE file — Path to a Node.js module which will be loaded in place of the built-in REPL. Overriding this value to an empty string ('') will use the built-in REPL. Swap in your custom one, or don't. Your call. 💅
  • NODE_SKIP_PLATFORM_CHECK — When set to 1, the check for a supported platform is skipped during Node.js startup. Node.js might not execute correctly. Any issues encountered on unsupported platforms will not be fixed. So like, this is your chaotic choice and I'm just the messenger. 💀
  • NODE_TEST_CONTEXT — When set to 'child', test reporter options will be overridden and test output will be sent to stdout in the TAP format. If any other value is provided, Node.js makes no guarantees about the reporter format used or its stability. Little gremlin variable, honestly.
  • NODE_TLS_REJECT_UNAUTHORIZED — When set to 0, TLS certificate validation is disabled. ⚠️ Bestie. That's a security thing. Be careful, okay?
  • NODE_USE_ENV_PROXY — When enabled, Node.js parses the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables during startup, and tunnels requests over the specified proxy. This currently only affects requests sent over fetch(). Support for other built-in http and https methods is under way. So like, it's in its expanding era. 🦋
  • NODE_USE_SYSTEM_CA — Similar to --use-system-ca. Use the trusted CA certificates present in the system store, in addition to the certificates in the bundled Mozilla CA store and certificates from NODE_EXTRA_CA_CERTS. Trust everyone legit, basically. 🫶
  • NODE_V8_COVERAGE dir — When set, Node.js writes JavaScript code coverage information to dir. Receipts, but for your code.
  • OPENSSL_CONF file — Load an OpenSSL configuration file on startup. Among other uses, this can be used to enable FIPS-compliant crypto if Node.js is built with ./configure --openssl-fips. If the --openssl-config command-line option is used, this environment variable is ignored. Command line wins, periodt. ⭐
  • SSL_CERT_DIR dir — If --use-openssl-ca is enabled, this overrides and sets OpenSSL's directory containing trusted certificates.
  • SSL_CERT_FILE file — If --use-openssl-ca is enabled, this overrides and sets OpenSSL's file containing trusted certificates.
  • TZ — Specify the timezone configuration. Time is a construct, but timezones are real, unfortunately. 🕐
  • UV_THREADPOOL_SIZE size — Sets the number of threads used in libuv's threadpool to size. More threads = more chaos = more power, choose wisely. 🔥

💀 BUGS 💀

Bugs are tracked in GitHub Issues: https://github.com/nodejs/node/issues

So if something's acting up, that's where the group chat lives. Go report it, bestie — they're actually really nice about it. 🙈

Copyright Node.js contributors. Node.js is available under the MIT license.

Node.js also includes external libraries that are available under a variety of licenses. See https://github.com/nodejs/node/blob/HEAD/LICENSE for the full license text.

Legal stuff but make it readable. 📜✨

👑 SEE ALSO 👑

Okay that's the whole page bestie, you ate that. 💖 This particular vintage is dated 2018 and calls itself NODE(1) — so if you see that footer, you know exactly where you are. Go build something iconic. 🦋💅

📦 where this page comes from