NODE-22(1)

📦 version 22.23.1, in fedora 44

✨ NAME ✨

okay so the name is node 🌸 it's a server-side JavaScript runtime, which means it runs JS outside the browser 💻✨

🎀 SYNOPSIS 🎀

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

💅 DESCRIPTION 💅

Okay so Node.js is a set of libraries for JavaScript that lets it be used outside of the browser 🌈 It's mostly obsessed with making simple, easy-to-build network clients and servers, and it is literally iconic at it 🫶

Just run node with no arguments and boom, you're in a REPL 💜

🦋 OPTIONS 🦋

  • - — this is an alias for stdin, kinda like how - works in other command-line tools 🧚 The script gets read from stdin, and any leftover arguments get passed along to the script.
  • -- — this marks the end of the command-line options 💖 Everything after it goes to the script.

If you haven't given a script filename or an eval/print script before this, then the next argument becomes the script filename ✨

  • --abort-on-uncaught-exception — instead of exiting, Node aborts, and that generates a core file you can analyze later 💀
  • --allow-fs-read — allows file system read access when you're using the permission model 📂
  • --allow-fs-write — allows file system write access when you're using the permission model ✍️
  • --allow-addons — allows native addons when you're using the permission model 🔌
  • --allow-child-process — allows spawning processes when you're using the permission model 🌱
  • --allow-wasi — allows WASI execution when you're using the permission model 🦋
  • --allow-worker — allows creating worker threads when you're using the permission model 🧵
  • --completion-bash — prints a source-able bash completion script for Node.js 🐚✨
  • -C, --conditions string — uses custom conditional exports conditions 🎯 The string is what you pass in 🫶
  • --cpu-prof — starts the V8 CPU profiler on startup and writes the CPU profile to disk before exit 🔥 If you don't specify --cpu-prof-dir, the profile lands in your current working directory with a generated file name 📁
  • --cpu-prof-dir — the directory where CPU profiles from --cpu-prof get placed 🗂️ Its default is controlled by --diagnostic-dir.
  • --cpu-prof-interval — the sampling interval, in microseconds, for CPU profiles made with --cpu-prof ⏱️ The default is 1000.
  • --cpu-prof-name — the file name of the V8 CPU profile generated with --cpu-prof 🏷️
  • --diagnostic-dir — sets the directory for all diagnostic output files 🩺 The default is the current working directory, which is also where all diagnostic output gets written by default. It also decides the default output directory for --cpu-prof-dir, --heap-prof-dir, and --redirect-warnings 💅
  • --disable-proto=mode — disables the Object.prototype.__proto__ property 🙈 If mode is delete, the property gets removed entirely. If mode is throw, touching the property throws an exception with the code ERR_PROTO_ACCESS 💥
  • --disable-wasm-trap-handler=mode — disables trap-handler-based WebAssembly bound checks and falls back to inline bound checks instead 🧠 This lets WebAssembly run with limited virtual memory 🌸
  • --disallow-code-generation-from-strings — makes built-in features like eval and new Function, which generate code from strings, throw an exception instead 🚫 This does not touch the Node.js vm module 🫠
  • --enable-fips — enables FIPS-compliant crypto at startup 🔐 This requires Node.js to be built with ./configure --openssl-fips.
  • --enable-source-maps — enables Source Map V3 support for stack traces 🗺️
  • --entry-url — interprets the entry point as a URL 🔗
  • --experimental-addon-modules — enables experimental addon module support 🧪
  • --experimental-default-type=type — interprets input from --eval or STDIN as either ES modules or CommonJS modules, but only when --input-type isn't specified 🎀
  • --experimental-config-file — specifies the configuration file to load 📜
  • --experimental-default-config-file — enables automatic loading of node.config.json 🪄
  • --experimental-import-meta-resolve — enables experimental ES modules support for import.meta.resolve() ✨
  • --experimental-loader=module — specifies the module to use as a custom module loader 🧳
  • --permission — enables the permission model 🛡️
  • --experimental-shadow-realm — use this to turn on ShadowRealm support 👻
  • --experimental-test-coverage — enables code coverage in the test runner 📊
  • --experimental-test-isolation=mode — configures the type of test isolation the test runner uses 🧼
  • --experimental-test-module-mocks — enables module mocking in the test runner 🎭
  • --experimental-transform-types — enables transforming TypeScript-only syntax into JavaScript 🔄
  • --experimental-eventsource — enables experimental support for the EventSource Web API 📡
  • --no-experimental-fetch — disables experimental support for the Fetch API 🚫
  • --no-experimental-websocket — disables experimental support for the WebSocket API 🔌🚫
  • --experimental-webstorage — enables experimental support for the Web Storage API 💾
  • --no-experimental-global-customevent — stops CustomEvent from being exposed on the global scope 🙅
  • --no-experimental-global-webcrypto — stops the Web Crypto API from being exposed on the global scope 🙅‍♀️
  • --no-experimental-repl-await — disables top-level await keyword support in the REPL 🌙
  • --no-experimental-sqlite — disables the experimental node:sqlite module 🗃️🚫
  • --no-experimental-strip-types — disables experimental type-stripping for TypeScript files 🧷
  • --experimental-vm-modules — enables experimental ES module support in the VM module 🧪🧩
  • --experimental-wasi-unstable-preview1 — enables experimental WebAssembly System Interface support 🦋 You don't need this flag anymore, since WASI is enabled by default now 💅
  • --experimental-inspector-network-resource — enables experimental support for inspector network resources 🕸️
  • --force-context-aware — disables loading native addons that aren't context-aware 🚷
  • --force-fips — forces FIPS-compliant crypto on startup 🔒 It cannot be turned off from script code, so it's a hard lock 😤 It has the same requirements as --enable-fips.
  • --frozen-intrinsics — enables experimental frozen intrinsics support 🧊
  • --heapsnapshot-near-heap-limit=max_count — generates a heap snapshot when V8 heap usage is getting close to the heap limit 📸 No more than the number of snapshots you specify (max_count) will be generated.
  • --heapsnapshot-signal=signal — generates a heap snapshot when the specified signal arrives 🚨
  • --heap-prof — starts the V8 heap profiler on startup and writes the heap profile to disk before exit 🧁 If you don't specify --heap-prof-dir, it goes to the current working directory with a generated file name 📁
  • --heap-prof-dir — the directory where heap profiles from --heap-prof get placed 🗂️ Its default is controlled by --diagnostic-dir.
  • --heap-prof-interval — the average sampling interval, in bytes, for heap profiles made with --heap-prof 📏 The default is 512 * 1024.
  • --heap-prof-name — the file name of the V8 heap profile generated with --heap-prof 🏷️
  • --icu-data-dir=file — specifies the ICU data load path 🌍 This overrides NODE_ICU_DATA.
  • --input-type=type — sets the module resolution type for input coming in via --eval, --print, or STDIN 🎯
  • --inspect-brk=[host:]port — activates the inspector on host:port and breaks at the start of the user script 🛑
  • --inspect-port=[host:]port — sets the host:port used when the inspector is activated 🔌
  • --inspect-publish-uid=stderr,http — specifies how the inspector WebSocket URL gets exposed 📣 The valid values are stderr and http, and the default is stderr,http 💜
  • --inspect-wait=[host:]port — activates the inspector on host:port and waits for a debugger to attach 🧘
  • --inspect=[host:]port — activates the inspector on host:port 🔍 The default is 127.0.0.1:9229.

V8 Inspector integration lets you attach Chrome DevTools and IDEs to Node.js instances for debugging and profiling 🛠️ It uses the Chrome DevTools Protocol 🌸

  • --insecure-http-parser — uses an insecure HTTP parser that accepts invalid HTTP headers 🙈 This might let you interoperate with non-conformant HTTP implementations, but it can also allow request smuggling and other HTTP attacks that depend on invalid headers being accepted.
🚨 Avoid using this option. It opens the door to request smuggling and other attacks, so please don't 😭
  • --jitless — disables runtime allocation of executable memory 🐢 Some platforms may need this for security reasons. It can also shrink the attack surface on other platforms, but the performance hit may be severe 💀

This flag is inherited from V8 and is subject to change upstream. It might 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 — sets the maximum size of HTTP headers in bytes 📏 It 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 📊 If you specify both this and --max-old-space-size, this one wins 👑 The percentage must be a number greater than 0 and up to 100, representing how much of the available system memory goes to the V8 heap.

Note: this flag uses --max-old-space-size, which may be unreliable on 32-bit platforms because of integer overflow issues 🙈

  • --napi-modules — this is a no-op 😴 It's only kept for compatibility.
  • --no-deprecation — silences deprecation warnings 🤫
  • --no-extra-info-on-fatal-exception — hides the extra information on a fatal exception that causes an exit 🫥
  • --no-force-async-hooks-checks — disables runtime checks for async_hooks 🧵 They'll still be turned on dynamically whenever async_hooks is enabled.
  • --no-addons — disables the node-addons exports condition and also disables loading native addons 🚫🔌 With --no-addons specified, calling process.dlopen or requiring a native C++ addon will fail and throw an exception 💥
  • --no-global-search-paths — 🙅‍♀️ Modules won't get searched in the global paths. Nope, not happening.
  • --no-warnings — 🔇 Silences every process warning, deprecations included. Shh 🤫
  • --node-memory-debug — 🧠 Turns on extra debug checks for memory leaks inside Node.js internals. Honestly this is mostly for developers debugging Node.js itself, so you probably won't need it, bestie 💀
  • --openssl-config=file — 🔐 Loads an OpenSSL configuration file on startup. One of the things it can do is turn on FIPS-compliant crypto, but only if Node.js was built with ./configure --openssl-fips. Very specific, very cool ✨
  • --pending-deprecation — ⏳ Emits pending deprecation warnings, so you get a heads up before stuff goes away 👀
  • --preserve-symlinks — 🔗 Tells the module loader to keep symbolic links intact when it resolves and caches modules that aren't the main module.
  • --preserve-symlinks-main — 🔗 Same vibe, but for the main module. The module loader keeps the symbolic links when resolving and caching it.
  • --prof — 📊 Generates V8 profiler output. Data time 🍓
  • --prof-process — 🧁 Processes V8 profiler output that was made with the V8 option --prof. Get the tea ☕
  • --redirect-warnings=file — 📝 Sends process warnings to the file you give it, instead of printing them to stderr. Keeps your terminal clean and cute 🎀
  • --report-compact — 📦 Writes diagnostic reports in a compact format, as single-line JSON. Tiny, tidy, no drama 💜
  • --report-dir, --report-directory — 📂 Sets the location where the diagnostic report gets generated. The file name can be an absolute path. If it isn't one, the default directory it lands in is controlled by --diagnostic-dir, which is another command-line option.
  • --report-filename — 🏷️ Names the file the diagnostic report will be written to.
  • --report-on-fatalerror — 💥 Lets the diagnostic report trigger on fatal errors, which are internal errors inside the Node.js runtime (like running out of memory) that end the application. It's amazing for checking out the heap, stack, event loop state, resource consumption and more, so you can figure out what went wrong 🔍
  • --report-on-signal — 📡 Lets a diagnostic report get generated when the running Node.js process receives a signal. You can pick the signal, or it uses the predefined one. The default signal is SIGUSR2.
  • --report-signal — 🎚️ Sets or resets the signal used for diagnostic report generation. Not supported on Windows 🪟 The default signal is SIGUSR2.
  • --report-uncaught-exception — 🙈 Lets a diagnostic report get generated for uncaught exceptions. It's super helpful when you want to look at the JavaScript stack next to the native stack and other runtime environment data.
  • --secure-heap=n — 🔒 Sets the size of the OpenSSL secure heap. Any value less than 2 turns the secure heap off. The default is 0, and the value has to be a power of two 🧮
  • --secure-heap-min=n — 🔐 Sets the minimum allocation from the OpenSSL secure heap. The default is 2, and the value has to be a power of two too.
  • --test — 🧪 Starts the Node.js command line test runner. Let's gooo ✅
  • --test-concurrency — 🏃‍♀️ The maximum number of test files the test runner CLI will run at the same time.
  • --test-coverage-branches=threshold — 🌿 Requires a minimum threshold for branch coverage, from 0 to 100.
  • --test-coverage-exclude — 🚫 A glob pattern that leaves matching files out of the coverage report.
  • --test-coverage-functions=threshold — 🧩 Requires a minimum threshold for function coverage, from 0 to 100.
  • --test-coverage-include — ✅ A glob pattern that only puts matching files into the coverage report.
  • --test-coverage-lines=threshold — 📏 Requires a minimum threshold for line coverage, from 0 to 100.
  • --test-force-exit — 🚪 Tells the test runner to exit the process once all the known tests are done, even if the event loop would otherwise stay active. Bye bye 👋
  • --test-name-pattern — 🔎 A regular expression that makes the test runner only run tests whose name matches the pattern.
  • --test-reporter — 📣 The test reporter to use when running tests.
  • --test-reporter-destination — 🗂️ The destination for the matching test reporter.
  • --test-only — ⭐ Makes the test runner only run the top-level tests that have the only option set. Main character energy 👑
  • --test-shard — 🍰 The test suite shard to run, in the format <index>/<total>.
  • --test-skip-pattern — 🙅 A regular expression that makes the test runner skip tests whose name matches the pattern.
  • --test-timeout — ⏰ The number of milliseconds the test execution will fail after.
  • --test-update-snapshots — 📸 Regenerates the snapshot file the test runner uses for snapshot testing. Fresh pics only 🫶
  • --throw-deprecation — 💣 Throws errors for deprecations instead of just warning about them. Spicy 🌶️
  • --title=title — 🏷️ Sets process.title on startup.
  • --tls-cipher-list=list — 🔑 Sets an alternative default TLS cipher list. This needs 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, so software like Wireshark can use it to decrypt the TLS traffic 🦈
  • --tls-max-v1.2 — 🕰️ Sets the default maxVersion to 'TLSv1.2'. Use it to turn off support for TLSv1.3.
  • --tls-max-v1.3 — 🚀 Sets the default maxVersion to 'TLSv1.3'. Use it to turn on support for TLSv1.3.
  • --tls-min-v1.0 — 🦕 Sets the default minVersion to 'TLSv1'. Use it for compatibility with old TLS clients or servers.
  • --tls-min-v1.1 — 🦖 Sets the default minVersion to 'TLSv1.1'. Use it 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 still supported so older Node.js versions stay happy.
  • --tls-min-v1.3 — 🛡️ Sets the default minVersion to 'TLSv1.3'. Use it to turn off 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, so maybe don't get too attached 💔
  • --trace-deprecation — 🔍 Prints stack traces for deprecations.
  • --trace-event-categories categories — 🏷️ A comma-separated list of categories to trace when trace event tracing is turned on using --trace-events-enabled.
  • --trace-event-file-pattern pattern — 🗺️ A template string that specifies the filepath for the trace event data. It supports ${rotation} and ${pid}.
  • --trace-events-enabled — 📼 Turns on the collection of trace event tracing information.
  • --trace-exit — 🚨 Prints a stack trace whenever an environment is exited proactively, which means invoking process.exit().
  • --trace-sigint — ✋ Prints a stack trace on SIGINT.
  • --trace-sync-io — 🐢 Prints a stack trace whenever synchronous I/O gets detected after the first turn of the event loop. Slow and steady, but we see you 👀
  • --trace-tls — 🔐 Prints TLS packet trace information to stderr.
  • --trace-uncaught — 🕵️‍♀️ Prints stack traces for uncaught exceptions. Usually you get the stack trace from when the Error got created, but this makes Node.js print the stack trace from where the value got thrown too. The thrown value doesn't have to be an Error instance, either.

Heads up though: turning this on may hurt garbage collection behaviour.

  • --trace-warnings — ⚠️ Prints stack traces for process warnings, deprecations included.
  • --track-heap-objects — 🧺 Tracks heap object allocations for heap snapshots.
  • --unhandled-rejections=mode — 🙋‍♀️ Defines how unhandled rejections get handled. It can be strict (raises an error), warn (enforces warnings), or none (silences warnings).
  • --use-bundled-ca, --use-openssl-ca — 🏦 Picks the CA store. You can use the bundled Mozilla CA store that ships with the current Node.js version, or OpenSSL's default CA store. The default store can be picked at build-time.

The bundled CA store is a snapshot of the Mozilla CA store, fixed at release time. It's identical on all supported platforms, so no surprises 💅

Using the OpenSSL store lets external changes to the store show up. On most Linux and BSD distributions, the distribution maintainers and system administrators look after this store. The OpenSSL CA store location depends on how the OpenSSL library is configured, but you can change it at runtime with environment variables.

See SSL_CERT_DIR and SSL_CERT_FILE. 🌸

  • --use-env-proxy — 🌐 Parses proxy settings from the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables, then applies them to the global HTTP/HTTPS clients.
  • --use-system-ca — 🖥️ Uses the trusted CA certificates in the system store, along with the certificates in the bundled Mozilla CA store and the certificates from NODE_EXTRA_CA_CERTS. On Windows and macOS it uses system APIs to bring in extra trusted certificates. On other platforms it's similar to --use-openssl-ca, except it caches the certificates on first load, and the system certificates get added alongside the others instead of replacing them. This flag supersedes --use-openssl-ca 🫧
  • --use-largepages=mode — 📄 Re-maps the Node.js static code onto large memory pages at startup. If the target system supports it, the static code moves onto 2 MiB pages instead of 4 KiB pages.

mode has to be one of these values: off (the default, which means don't map), on (map and ignore failure, reporting it to stderr), or silent (map and quietly ignore failure).

  • --v8-options — 📜 Prints the V8 command-line options.
  • --v8-pool-size=num — 🧵 Sets V8's thread pool size, which gets used to allocate background jobs. If it's set to 0, V8 picks an appropriate thread pool size based on the number of online processors. If the value is larger than V8's maximum, the largest value gets chosen instead.
  • --watch — 👀 Starts Node.js in watch mode. In watch mode, changes to the watched files make the Node.js process restart 🔄

By default, watch mode keeps an eye on the entry point and any required or imported module, lowkey the whole crew. If you want to pick exactly which paths get watched, reach for --watch-path 👀

🦋 --watch-path

Starts Node.js in watch mode and tells it which paths to watch 🎀. Once you're in watch mode, any change in those watched paths makes the Node.js process restart, so you get that fresh-start glow-up automatically ✨

Heads up, bestie: using this turns off watching for required or imported modules, even if you pair it with --watch 🙈

🌷 --watch-kill-signal

Lets you customize the signal that gets sent to the process whenever watch mode restarts it 💅

🫧 --zero-fill-buffers

Automatically zero-fills every newly allocated Buffer and SlowBuffer instance. Clean slate, every time 🧼💖

🔍 -c, --check

Checks the script's syntax without actually running it 🧐. If the script is invalid, it exits with an error code, so you'll know immediately that something's sus 💀

🍓 -e, --eval string

Evaluates string as JavaScript. Main character energy 👑

🩺 -h, --help

Prints the command-line options 📋. Real talk though, the output here is less detailed than this document, so if you want the full tea, read the whole thing 🫶

🐣 -i, --interactive

Opens the REPL even when stdin doesn't look like a terminal 💜

🖨️ -p, --print string

Exactly the same as -e, except it also prints the result ✨

📦 -r, --require module

Preloads the specified module at startup 🚀. It follows require()'s module resolution rules, and module can be either a path to a file or a Node.js module name. Very organized, very iconic 🗂️

🏷️ -v, --version

Prints node's version 🎉

🌸 ENVIRONMENT 🌸

Okay so these are the environment variables, and they're giving a lot 🌈

  • FORCE_COLOR — This turns on ANSI colorized output 🎨. The value can be 1, true, or an empty string for 16-color support, 2 for 256-color support, or 3 for 16 million-color support. When it's used and set to a supported value, both NO_COLOR and NODE_DISABLE_COLORS get ignored. Any other value means colorized output is disabled, no cap 🙅‍♀️
  • NO_COLOR — Just an alias for NODE_DISABLE_COLORS 🤍
  • NODE_COMPILE_CACHE dir — Enables the module compile cache for the Node.js instance 🗃️
  • NODE_DEBUG modules... — A comma-separated list of core modules that should print debug information 🐛
  • NODE_DEBUG_NATIVE modules... — A comma-separated list of C++ core modules that should print debug information 🔧
  • NODE_DISABLE_COMPILE_CACHE — Disables the module compile cache for the Node.js instance 🚫
  • NODE_DISABLE_COLORS — When set to 1, colors won't be used in the REPL 🙊
  • NODE_EXTRA_CA_CERTS file — When this is set, the well-known "root" CAs (like VeriSign) get extended with the extra certificates in file 🔐. The file should contain one or more trusted certificates in PEM format.

If file is missing or misformatted, a message gets emitted once using process.emitWarning(), but any other errors are ignored.

This variable is ignored when node runs as setuid root or has Linux file capabilities set 🙅.

NODE_EXTRA_CA_CERTS is only read when the Node.js process first launches. Changing the value at runtime with process.env.NODE_EXTRA_CA_CERTS does absolutely nothing to the current process 💀

  • NODE_ICU_DATA file — The data path for ICU (Intl object) data 🌍. It extends linked-in data when compiled with small-icu support.
  • NODE_NO_WARNINGS — When set to 1, process warnings get silenced 🤫
  • NODE_OPTIONS options... — A space-separated list of command-line options 📝. They're interpreted as if you had typed them on the command line before the actual command, so they can be overridden. Node.js exits with an error if you use an option that isn't allowed in the environment, like --print or a script file 🚨
  • NODE_PATH directories... — A colon-separated list of directories that get prefixed to the module search path 🗺️
  • NODE_PENDING_DEPRECATION — When set to 1, pending deprecation warnings get emitted ⚠️
  • NODE_PENDING_PIPE_INSTANCES — Sets the number of pending pipe instance handles while the pipe server is waiting for connections 🪟. This one is Windows only.
  • NODE_PRESERVE_SYMLINKS — When set to 1, the module loader keeps symbolic links intact while resolving and caching modules 🔗
  • NODE_REDIRECT_WARNINGS file — Writes process warnings to the given file instead of printing them to stderr 📄. It's the same as passing --redirect-warnings file on the command line.
  • NODE_REPL_HISTORY file — The path to the file where persistent REPL history gets stored 📚. The default is ~/.node_repl_history, but this variable overrides it. Setting it to an empty string ("" or " ") turns persistent REPL history off 🚫
  • NODE_REPL_EXTERNAL_MODULE file — The path to a Node.js module that gets loaded in place of the built-in REPL 🧩. Setting this to an empty string ('') brings back the built-in REPL.
  • NODE_SKIP_PLATFORM_CHECK — When set to 1, the supported-platform check gets skipped during startup 🙃. Node.js might not run correctly, and any issues on unsupported platforms won't be fixed. Proceed with caution, bestie 😬
  • NODE_TEST_CONTEXT — When set to 'child', test reporter options get overridden and the test output goes to stdout in TAP format 🧪. If any other value is provided, Node.js makes no guarantees about the reporter format or its stability.
  • NODE_TLS_REJECT_UNAUTHORIZED — When set to 0, TLS certificate validation is disabled 🚨. Yikes, be careful with this one.
  • 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 still under way 🚧

  • NODE_USE_SYSTEM_CA — Similar to --use-system-ca 🏛️. It uses the trusted CA certificates in the system store, on top of the certificates in the bundled Mozilla CA store and the certificates from NODE_EXTRA_CA_CERTS.
  • NODE_V8_COVERAGE dir — When set, Node.js writes JavaScript code coverage information to dir 📊
  • OPENSSL_CONF file — Loads an OpenSSL configuration file on startup 🔑. Among other uses, this can 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 gets ignored.

  • 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 — Specifies the timezone configuration 🕰️
  • UV_THREADPOOL_SIZE size — Sets the number of threads used in libuv's threadpool to size 🧵

🐛 BUGS 🐛

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

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 📖

🔗 SEE ALSO 🔗

That's the whole page, bestie! 🧚✨ Stamped 2018 and filed under NODE(1), so it's officially a vintage classic now 💅🌸

📦 where this page comes from