Главная страница » Как узнать версию node js в консоли

Как узнать версию node js в консоли

  • автор:

How to check version in Node.js? Check Node version from command line

How to check version in Node.js? Check Node version from command line

You might use node.js for many of your projects. But do you know how to find the version of node.js? If not, you are in the right place.

Software developers are working every day on adding new features, fixing bugs & patching vulnerabilities to their software. This is because no software is perfect on the very first release. So they roll out various releases, and to differentiate between them, they use version numbers.

Like other software, Node.js too has a lot of versions. Where can we find them? Just visit github.com/nodejs/node/releases and click on tags.

Github page showing the various versions of Node.js available.

Versions of Node.js

As of now, it seems like v18.8.0 is the latest version.

Knowing the version of your node is important because:

  1. You might be working on a project which requires a different node version. In that case to make sure everything works perfectly on your end you have to match that particular node version.
  2. If you are stuck at an older version of node, it might be that your project has some vulnerabilities or security risks. You might also be missing out on some of the improvements that may be implemented in the recent versions. So, you can check if your version is the latest. If not you should update your node.js.

What is Node.js?

Node.js is a JavaScript runtime built on Chrome’s V8 JavaScript engine. It’s used for developing server-side applications and for executing JavaScript code outside of a browser.

Read this blog “What is Node.js? – Introduction” to know more about Node.js.

Initial Setup

If you don’t have Node.js installed on your local machine, don’t worry, Codedamn got you covered.

If you already have Node.js installed on your local machine, then you can skip this section.

1. Visit the Codedamn Playground and select Node.js.

Codedamn Playground

Codedamn Playground

2. Give your playground a name. I will set it to “check-node-version”. Now, click on “Create Playground”.

Set your playground name

3. It should open up a web IDE with a terminal at the bottom. Press Ctrl+C to stop the current process that is running.

Codedamn IDE with terminal at the bottom

Codedamn IDE with a terminal at the bottom

Now you have a system with Node.js installed.

Determining the version of Node.js

It’s actually very simple. And you don’t even have to remember anything.

Most of the command line tools have a help flag. Running the command with this flag gives us a manual on how to use the tool. So just type node —help and you will get a list of all the available flags.

node --help output

node –help output

There will be a lot of information, but all we need to search for is “version”. Right at the bottom, you will find the flag for the version.

node version flag in help

node version flag in help

So, the flag to get the version is —version or -v . So just type node -v and you will get the version of Node.js you are using.

node version

node version

So, this means that I am using version 16.17.0 of Node.js. This might be different from the version you are using.

Even though the steps mentioned in this article are very specific to Node.js, they can still be applied to most of the command line tools.

Conclusion

So, in this article, we learned the importance of versions and why we should keep our software updated. We learned some tips on how to find the relevant flags of a command. To find the version of the node that we are using, we use the flag —version or -v .

Free money-back guarantee

Unlimited access to all platform courses

100+ practice projects included

ChatGPT Based Instant AI Help

Structured Node.js Full-Stack Roadmap To Get A Job

Exclusive community for events, workshops

Sharing is caring

Did you like what Arnab Sen wrote? Thank them for their work by sharing it on social media.

Node.js v19.8.1 documentation

Node.js comes with a variety of CLI options. These options expose built-in debugging, multiple ways to execute scripts, and other helpful runtime options.

To view this documentation as a manual page in a terminal, run man node .

Synopsis #

node [options] [V8 options] [<program-entry-point> | -e «script» | -] [—] [arguments]

node inspect [<program-entry-point> | -e «script» | <host>:<port>] …

Execute without arguments to start the REPL.

For more info about node inspect , see the debugger documentation.

Program entry point #

The program entry point is a specifier-like string. If the string is not an absolute path, it’s resolved as a relative path from the current working directory. That path is then resolved by CommonJS module loader. If no corresponding file is found, an error is thrown.

If a file is found, its path will be passed to the ECMAScript module loader under any of the following conditions:

  • The program was started with a command-line flag that forces the entry point to be loaded with ECMAScript module loader.
  • The file has an .mjs extension.
  • The file does not have a .cjs extension, and the nearest parent package.json file contains a top-level «type» field with a value of «module» .

Otherwise, the file is loaded using the CommonJS module loader. See Modules loaders for more details.

ECMAScript modules loader entry point caveat #

When loading ECMAScript module loader loads the program entry point, the node command will only accept as input only files with .js , .mjs , or .cjs extensions; and with .wasm extensions when —experimental-wasm-modules is enabled.

Options #

Underscores instead of dashes are now allowed for Node.js options as well, in addition to V8 options.

All options, including V8 options, allow words to be separated by both dashes ( — ) or underscores ( _ ). For example, —pending-deprecation is equivalent to —pending_deprecation .

If an option that takes a single value (such as —max-http-header-size ) is passed more than once, then the last passed value is used. Options from the command line take precedence over options passed through the NODE_OPTIONS environment variable.

Alias for stdin. Analogous to the use of — in other command-line utilities, meaning that the script is read from stdin, and the rest of the options are passed to that script.

Indicate the end of node options. Pass the rest of the arguments to the script. If no script filename or eval/print script is supplied prior to this, then the next argument is used as a script filename.

—abort-on-uncaught-exception #

Aborting instead of exiting causes a core file to be generated for post-mortem analysis using a debugger (such as lldb , gdb , and mdb ).

If this flag is passed, the behavior can still be set to not abort through process.setUncaughtExceptionCaptureCallback() (and through usage of the node:domain module that uses it).

—build-snapshot #

Generates a snapshot blob when the process exits and writes it to disk, which can be loaded later with —snapshot-blob .

When building the snapshot, if —snapshot-blob is not specified, the generated blob will be written, by default, to snapshot.blob in the current working directory. Otherwise it will be written to the path specified by —snapshot-blob .

The v8.startupSnapshot API can be used to specify an entry point at snapshot building time, thus avoiding the need of an additional entry script at deserialization time:

For more information, check out the v8.startupSnapshot API documentation.

Currently the support for run-time snapshot is experimental in that:

  1. User-land modules are not yet supported in the snapshot, so only one single file can be snapshotted. Users can bundle their applications into a single script with their bundler of choice before building a snapshot, however.
  2. Only a subset of the built-in modules work in the snapshot, though the Node.js core test suite checks that a few fairly complex applications can be snapshotted. Support for more modules are being added. If any crashes or buggy behaviors occur when building a snapshot, please file a report in the Node.js issue tracker and link to it in the tracking issue for user-land snapshots.
—completion-bash #

Print source-able bash completion script for Node.js.

-C condition , —conditions=condition #

Enable experimental support for custom conditional exports resolution conditions.

Any number of custom string condition names are permitted.

The default Node.js conditions of «node» , «default» , «import» , and «require» will always apply as defined.

For example, to run a module with «development» resolutions:

—cpu-prof #

Starts the V8 CPU profiler on start up, and writes the CPU profile to disk before exit.

If —cpu-prof-dir is not specified, the generated profile is placed in the current working directory.

If —cpu-prof-name is not specified, the generated profile is named CPU.$.$.$.$.$.cpuprofile .

—cpu-prof-dir #

Specify 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 #

Specify the sampling interval in microseconds for the CPU profiles generated by —cpu-prof . The default is 1000 microseconds.

—cpu-prof-name #

Specify the file name of the CPU profile generated by —cpu-prof .

—diagnostic-dir=directory #

Set the directory to which all diagnostic output files are written. Defaults to current working directory.

Affects the default output directory of:

—disable-proto=mode #

Disable the Object.prototype.__proto__ property. If mode is delete , the property is removed entirely. If mode is throw , accesses to the property throw an exception with the code ERR_PROTO_ACCESS .

—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 node:vm module.

—dns-result-order=order #

Changed default value to verbatim .

Added in: v16.4.0, v14.18.0

Set the default value of verbatim in dns.lookup() and dnsPromises.lookup() . The value could be:

  • ipv4first : sets default verbatim false .
  • verbatim : sets default verbatim true .

The default is verbatim and dns.setDefaultResultOrder() have higher priority than —dns-result-order .

—enable-fips #

Enable FIPS-compliant crypto at startup. (Requires Node.js to be built against FIPS-compatible OpenSSL.)

—enable-network-family-autoselection #

Enables the family autoselection algorithm unless connection options explicitly disables it.

—enable-source-maps #

This API is no longer experimental.

Added in: v12.12.0

Enable Source Map v3 support for stack traces.

When using a transpiler, such as TypeScript, stack traces thrown by an application reference the transpiled code, not the original source position. —enable-source-maps enables caching of Source Maps and makes a best effort to report stack traces relative to the original source file.

Overriding Error.prepareStackTrace prevents —enable-source-maps from modifying the stack trace.

Note, enabling source maps can introduce latency to your application when Error.stack is accessed. If you access Error.stack frequently in your application, take into account the performance implications of —enable-source-maps .

—experimental-import-meta-resolve #

Enable experimental import.meta.resolve() support.

—experimental-loader=module #

This flag was renamed from —loader to —experimental-loader .

Specify the module of a custom experimental ECMAScript module loader. module may be any string accepted as an import specifier.

—experimental-network-imports #

Enable experimental support for the https: protocol in import specifiers.

—experimental-policy #

Use the specified file as a security policy.

—no-experimental-fetch #

Disable experimental support for the Fetch API.

—no-experimental-global-webcrypto #

Disable exposition of Web Crypto API on the global scope.

—no-experimental-global-customevent #

Disable exposition of CustomEvent Web API on the global scope.

—no-experimental-repl-await #

Use this flag to disable top-level await in REPL.

—experimental-shadow-realm #

Use this flag to enable ShadowRealm support.

—experimental-test-coverage #

When used in conjunction with the node:test module, a code coverage report is generated as part of the test runner output. If no tests are run, a coverage report is not generated. See the documentation on collecting code coverage from tests for more details.

—experimental-vm-modules #

Enable experimental ES Module support in the node:vm module.

—experimental-wasi-unstable-preview1 #

changed from —experimental-wasi-unstable-preview0 to —experimental-wasi-unstable-preview1 .

Added in: v13.3.0, v12.16.0

Enable experimental WebAssembly System Interface (WASI) support.

—experimental-wasm-modules #

Enable experimental WebAssembly module support.

—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 .)

—frozen-intrinsics #

Enable experimental frozen intrinsics like Array and Object .

Only the root context is supported. There is no guarantee that globalThis.Array is indeed the default intrinsic reference. Code may break under this flag.

To allow polyfills to be added, —require and —import both run before freezing intrinsics.

—force-node-api-uncaught-exceptions-policy #

Enforces uncaughtException event on Node-API asynchronous callbacks.

To prevent from an existing add-on from crashing the process, this flag is not enabled by default. In the future, this flag will be enabled by default to enforce the correct behavior.

—heapsnapshot-near-heap-limit=max_count #

Writes a V8 heap snapshot to disk when the V8 heap usage is approaching the heap limit. count should be a non-negative integer (in which case Node.js will write no more than max_count snapshots to disk).

When generating snapshots, garbage collection may be triggered and bring the heap usage down. Therefore multiple snapshots may be written to disk before the Node.js instance finally runs out of memory. These heap snapshots can be compared to determine what objects are being allocated during the time consecutive snapshots are taken. It’s not guaranteed that Node.js will write exactly max_count snapshots to disk, but it will try its best to generate at least one and up to max_count snapshots before the Node.js instance runs out of memory when max_count is greater than 0 .

Generating V8 snapshots takes time and memory (both memory managed by the V8 heap and native memory outside the V8 heap). The bigger the heap is, the more resources it needs. Node.js will adjust the V8 heap to accommodate the additional V8 heap memory overhead, and try its best to avoid using up all the memory available to the process. When the process uses more memory than the system deems appropriate, the process may be terminated abruptly by the system, depending on the system configuration.

—heapsnapshot-signal=signal #

Enables a signal handler that causes the Node.js process to write a heap dump when the specified signal is received. signal must be a valid signal name. Disabled by default.

—heap-prof #

Starts the V8 heap profiler on start up, and writes the heap profile to disk before exit.

If —heap-prof-dir is not specified, the generated profile is placed in the current working directory.

If —heap-prof-name is not specified, the generated profile is named Heap.$.$.$.$.$.heapprofile .

—heap-prof-dir #

Specify 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 #

Specify the average sampling interval in bytes for the heap profiles generated by —heap-prof . The default is 512 * 1024 bytes.

—heap-prof-name #

Specify the file name of the heap profile generated by —heap-prof .

—icu-data-dir=file #

Specify ICU data load path. (Overrides NODE_ICU_DATA .)

—import=module #

Preload the specified module at startup.

Follows ECMAScript module resolution rules. Use —require to load a CommonJS module. Modules preloaded with —require will run before modules preloaded with —import .

—input-type=type #

This configures Node.js to interpret string input as CommonJS or as an ES module. String input is input via —eval , —print , or STDIN .

Valid values are «commonjs» and «module» . The default is «commonjs» .

The REPL does not support this option.

—inspect-brk[=[host:]port] #

Activate inspector on host:port and break at start of user script. Default host:port is 127.0.0.1:9229 .

—inspect-port=[host:]port #

Set the host:port to be used when the inspector is activated. Useful when activating the inspector by sending the SIGUSR1 signal.

Default host is 127.0.0.1 .

See the security warning below regarding the host parameter usage.

—inspect[=[host:]port] #

Activate inspector on host:port . Default is 127.0.0.1:9229 .

V8 inspector integration allows tools such as Chrome DevTools and IDEs to debug and profile Node.js instances. The tools attach to Node.js instances via a tcp port and communicate using the Chrome DevTools Protocol.

Warning: binding inspector to a public IP:port combination is insecure #

Binding the inspector to a public IP (including 0.0.0.0 ) with an open port is insecure, as it allows external hosts to connect to the inspector and perform a remote code execution attack.

If specifying a host, make sure that either:

  • The host is not accessible from public networks.
  • A firewall disallows unwanted connections on the port.

More specifically, —inspect=0.0.0.0 is insecure if the port ( 9229 by default) is not firewall-protected.

See the debugging security implications section for more information.

—inspect-publish-uid=stderr,http #

Specify ways of the inspector web socket url exposure.

By default inspector websocket url is available in stderr and under /json/list endpoint on http://host:port/json/list .

—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.

—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.

—max-http-header-size=size #

Change maximum default size of HTTP headers from 8 KiB to 16 KiB.

Added in: v11.6.0, v10.15.0

Specify the maximum size, in bytes, of HTTP headers. Defaults to 16 KiB.

—napi-modules #

This option is a no-op. It is kept for compatibility.

—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.

—no-deprecation #

Silence deprecation warnings.

—no-extra-info-on-fatal-exception #

Hide extra information on fatal exception that causes exit.

—no-force-async-hooks-checks #

Disables runtime checks for async_hooks . These will still be enabled dynamically when async_hooks is enabled.

—no-global-search-paths #

Do not search modules from global paths like $HOME/.node_modules and $NODE_PATH .

—no-warnings #

Silence all process warnings (including deprecations).

—node-memory-debug #

Enable extra debug checks for memory leaks in Node.js internals. This is usually only useful for developers debugging Node.js itself.

—openssl-config=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 against FIPS-enabled OpenSSL.

—openssl-shared-config #

Enable OpenSSL default configuration section, openssl_conf to be read from the OpenSSL configuration file. The default configuration file is named openssl.cnf but this can be changed using the environment variable OPENSSL_CONF , or by using the command line option —openssl-config . The location of the default OpenSSL configuration file depends on how OpenSSL is being linked to Node.js. Sharing the OpenSSL configuration may have unwanted implications and it is recommended to use a configuration section specific to Node.js which is nodejs_conf and is default when this option is not used.

—openssl-legacy-provider #

Enable OpenSSL 3.0 legacy provider. For more information please see OSSL_PROVIDER-legacy.

—pending-deprecation #

Emit pending deprecation warnings.

Pending deprecations are generally identical to a runtime deprecation with the notable exception that they are turned off by default and will not be emitted unless either the —pending-deprecation command-line flag, or the NODE_PENDING_DEPRECATION=1 environment variable, is set. Pending deprecations are used to provide a kind of selective «early warning» mechanism that developers may leverage to detect deprecated API usage.

—policy-integrity=sri #

Instructs Node.js to error prior to running any code if the policy does not have the specified integrity. It expects a Subresource Integrity string as a parameter.

—preserve-symlinks #

Instructs the module loader to preserve symbolic links when resolving and caching modules.

By default, when Node.js loads a module from a path that is symbolically linked to a different on-disk location, Node.js will dereference the link and use the actual on-disk «real path» of the module as both an identifier and as a root path to locate other dependency modules. In most cases, this default behavior is acceptable. However, when using symbolically linked peer dependencies, as illustrated in the example below, the default behavior causes an exception to be thrown if moduleA attempts to require moduleB as a peer dependency:

The —preserve-symlinks command-line flag instructs Node.js to use the symlink path for modules as opposed to the real path, allowing symbolically linked peer dependencies to be found.

Note, however, that using —preserve-symlinks can have other side effects. Specifically, symbolically linked native modules can fail to load if those are linked from more than one location in the dependency tree (Node.js would see those as two separate modules and would attempt to load the module multiple times, causing an exception to be thrown).

The —preserve-symlinks flag does not apply to the main module, which allows node —preserve-symlinks node_module/.bin/<foo> to work. To apply the same behavior for the main module, also use —preserve-symlinks-main .

—preserve-symlinks-main #

Instructs the module loader to preserve symbolic links when resolving and caching the main module ( require.main ).

This flag exists so that the main module can be opted-in to the same behavior that —preserve-symlinks gives to all other imports; they are separate flags, however, for backward compatibility with older Node.js versions.

—preserve-symlinks-main does not imply —preserve-symlinks ; use —preserve-symlinks-main in addition to —preserve-symlinks when it is not desirable to follow symlinks before resolving relative paths.

See —preserve-symlinks for more information.

Generate V8 profiler output.

—prof-process #

Process V8 profiler output generated using the V8 option —prof .

—redirect-warnings=file #

Write process warnings to the given file instead of printing to stderr. The file will be created if it does not exist, and will be appended to if it does. If an error occurs while attempting to write the warning to the file, the warning will be written to stderr instead.

The file name may be an absolute path. If it is not, the default directory it will be written to is controlled by the —diagnostic-dir command-line option.

—report-compact #

Write reports in a compact format, single-line JSON, more easily consumable by log processing systems than the default multi-line format designed for human consumption.

—report-dir=directory , report-directory=directory #

This option is no longer experimental.

Changed from —diagnostic-report-directory to —report-directory .

Location at which the report will be generated.

—report-filename=filename #

This option is no longer experimental.

changed from —diagnostic-report-filename to —report-filename .

Name of the file to which the report will be written.

If the filename is set to ‘stdout’ or ‘stderr’ , the report is written to the stdout or stderr of the process respectively.

—report-on-fatalerror #

This option is no longer experimental.

changed from —diagnostic-report-on-fatalerror to —report-on-fatalerror .

Enables the report to be triggered on fatal errors (internal errors within the Node.js runtime such as out of memory) that lead to termination of the application. Useful to inspect various diagnostic data elements such as heap, stack, event loop state, resource consumption etc. to reason about the fatal error.

—report-on-signal #

This option is no longer experimental.

changed from —diagnostic-report-on-signal to —report-on-signal .

Enables report to be generated upon receiving the specified (or predefined) signal to the running Node.js process. The signal to trigger the report is specified through —report-signal .

—report-signal=signal #

This option is no longer experimental.

changed from —diagnostic-report-signal to —report-signal .

Sets or resets the signal for report generation (not supported on Windows). Default signal is SIGUSR2 .

—report-uncaught-exception #

Report is not generated if the uncaught exception is handled.

This option is no longer experimental.

changed from —diagnostic-report-uncaught-exception to —report-uncaught-exception .

Enables report to be generated when the process exits due to an uncaught exception. Useful when inspecting the JavaScript stack in conjunction with native stack and other runtime environment data.

—secure-heap=n #

Initializes an OpenSSL secure heap of n bytes. When initialized, the secure heap is used for selected types of allocations within OpenSSL during key generation and other operations. This is useful, for instance, to prevent sensitive information from leaking due to pointer overruns or underruns.

The secure heap is a fixed size and cannot be resized at runtime so, if used, it is important to select a large enough heap to cover all application uses.

The heap size given must be a power of two. Any value less than 2 will disable the secure heap.

The secure heap is disabled by default.

The secure heap is not available on Windows.

—secure-heap-min=n #

When using —secure-heap , the —secure-heap-min flag specifies the minimum allocation from the secure heap. The minimum value is 2 . The maximum value is the lesser of —secure-heap or 2147483647 . The value given must be a power of two.

—snapshot-blob=path #

When used with —build-snapshot , —snapshot-blob specifies the path where the generated snapshot blob is written to. If not specified, the generated blob is written to snapshot.blob in the current working directory.

When used without —build-snapshot , —snapshot-blob specifies the path to the blob that is used to restore the application state.

When loading a snapshot, Node.js checks that:

  1. The version, architecture and platform of the running Node.js binary are exactly the same as that of the binary that generates the snapshot.
  2. The V8 flags and CPU features are compatible with that of the binary that generates the snapshot.

If they don’t match, Node.js refuses to load the snapshot and exits with status code 1.

Test runner now supports running in watch mode.

Added in: v18.1.0, v16.17.0

Starts the Node.js command line test runner. This flag cannot be combined with —watch-path , —check , —eval , —interactive , or the inspector. See the documentation on running tests from the command line for more details.

—test-name-pattern #

A regular expression that configures the test runner to only execute tests whose name matches the provided pattern. See the documentation on filtering tests by name for more details.

—test-reporter #

A test reporter to use when running tests. See the documentation on test reporters for more details.

—test-reporter-destination #

The destination for the corresponding test reporter. See the documentation on test reporters for more details.

—test-only #

Configures the test runner to only execute top level tests that have the only option set.

—throw-deprecation #

Throw errors for deprecations.

—title=title #

Set process.title on startup.

—tls-cipher-list=list #

Specify an alternative default TLS cipher list. Requires Node.js to be built with crypto support (default).

—tls-keylog=file #

Log TLS key material to a file. The key material is in NSS SSLKEYLOGFILE format and can be used by software (such as Wireshark) to decrypt the TLS traffic.

—tls-max-v1.2 #

Set tls.DEFAULT_MAX_VERSION to ‘TLSv1.2’. Use to disable support for TLSv1.3.

—tls-max-v1.3 #

Set default tls.DEFAULT_MAX_VERSION to ‘TLSv1.3’. Use to enable support for TLSv1.3.

—tls-min-v1.0 #

Set default tls.DEFAULT_MIN_VERSION to ‘TLSv1’. Use for compatibility with old TLS clients or servers.

—tls-min-v1.1 #

Set default tls.DEFAULT_MIN_VERSION to ‘TLSv1.1’. Use for compatibility with old TLS clients or servers.

—tls-min-v1.2 #

Set default tls.DEFAULT_MIN_VERSION 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 #

Set default tls.DEFAULT_MIN_VERSION to ‘TLSv1.3’. Use to disable support for TLSv1.2, which is not as secure as TLSv1.3.

—trace-atomics-wait #

Print short summaries of calls to Atomics.wait() to stderr. The output could look like this:

The fields here correspond to:

  • The thread id as given by worker_threads.threadId
  • The base address of the SharedArrayBuffer in question, as well as the byte offset corresponding to the index passed to Atomics.wait()
  • The expected value that was passed to Atomics.wait()
  • The timeout passed to Atomics.wait
—trace-deprecation #

Print stack traces for deprecations.

—trace-event-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 #

Template string specifying the filepath for the trace event data, it supports $ and $ .

—trace-events-enabled #

Enables the collection of trace event tracing information.

—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.

—trace-tls #

Prints TLS packet trace information to stderr . This can be used to debug TLS connection problems.

—trace-uncaught #

Print 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).

Enabling this option may affect garbage collection behavior negatively.

—trace-warnings #

Print stack traces for process warnings (including deprecations).

—track-heap-objects #

Track heap object allocations for heap snapshots.

—unhandled-rejections=mode #

Changed default mode to throw . Previously, a warning was emitted.

Added in: v12.0.0, v10.17.0

Using this flag allows to change what should happen when an unhandled rejection occurs. One of the following modes can be chosen:

  • throw : Emit unhandledRejection . If this hook is not set, raise the unhandled rejection as an uncaught exception. This is the default.
  • strict : Raise the unhandled rejection as an uncaught exception. If the exception is handled, unhandledRejection is emitted.
  • warn : Always trigger a warning, no matter if the unhandledRejection hook is set or not but do not print the deprecation warning.
  • warn-with-error-code : Emit unhandledRejection . If this hook is not set, trigger a warning, and set the process exit code to 1.
  • none : Silence all warnings.

If a rejection happens during the command line entry point’s ES module static loading phase, it will always raise it as an uncaught exception.

—use-bundled-ca , —use-openssl-ca #

Use bundled Mozilla CA store as supplied by current Node.js version or use OpenSSL’s default CA store. The default store is selectable at build-time.

The bundled CA store, as supplied by Node.js, is a snapshot of Mozilla CA store that is fixed at release time. It is identical on all supported platforms.

Using 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. OpenSSL CA store location is dependent on configuration of the OpenSSL library but this can be altered at runtime using environment variables.

See SSL_CERT_DIR and SSL_CERT_FILE .

—use-largepages=mode #

Re-map the Node.js static code to large memory pages at startup. If supported on the target system, this will cause the Node.js static code to be moved onto 2 MiB pages instead of 4 KiB pages.

The following values are valid for mode :

  • off : No mapping will be attempted. This is the default.
  • on : If supported by the OS, mapping will be attempted. Failure to map will be ignored and a message will be printed to standard error.
  • silent : If supported by the OS, mapping will be attempted. Failure to map will be ignored and will not be reported.
—v8-options #

Print V8 command-line options.

—v8-pool-size=num #

Set V8’s thread pool size which will be used to allocate background jobs.

If set to 0 then Node.js will choose an appropriate size of the thread pool based on an estimate of the amount of parallelism.

The amount of parallelism refers to the number of computations that can be carried out simultaneously in a given machine. In general, it’s the same as the amount of CPUs, but it may diverge in environments such as VMs or containers.

—watch #

Test runner now supports running in watch mode.

Added in: v18.11.0

Starts Node.js in watch mode. When in watch mode, changes in the watched files cause the Node.js process to restart. By default, watch mode will watch the entry point and any required or imported module. Use —watch-path to specify what paths to watch.

This flag cannot be combined with —check , —eval , —interactive , or the REPL.

—watch-path #

Starts Node.js in watch mode and specifies what paths to watch. When in watch mode, changes in the watched paths cause the Node.js process to restart. This will turn off watching of required or imported modules, even when used in combination with —watch .

This flag cannot be combined with —check , —eval , —interactive , —test , or the REPL.

This option is only supported on macOS and Windows. An ERR_FEATURE_UNAVAILABLE_ON_PLATFORM exception will be thrown when the option is used on a platform that does not support it.

—watch-preserve-output #

Disable the clearing of the console when watch mode restarts the process.

—zero-fill-buffers #

Automatically zero-fills all newly allocated Buffer and SlowBuffer instances.

-c , —check #

The —require option is now supported when checking a file.

Added in: v5.0.0, v4.2.0

Syntax check the script without executing.

-e , —eval «script» #

Built-in libraries are now available as predefined variables.

Evaluate the following argument as JavaScript. The modules which are predefined in the REPL can also be used in script .

On Windows, using cmd.exe a single quote will not work correctly because it only recognizes double » for quoting. In Powershell or Git bash, both ‘ and » are usable.

-h , —help #

Print node command-line options. The output of this option is less detailed than this document.

-i , —interactive #

Opens the REPL even if stdin does not appear to be a terminal.

-p , —print «script» #

Built-in libraries are now available as predefined variables.

Identical to -e but prints the result.

-r , —require module #

Preload the specified module at startup.

Follows require() ‘s module resolution rules. module may be either a path to a file, or a node module name.

Only CommonJS modules are supported. Use —import to preload an ECMAScript module. Modules preloaded with —require will run before modules preloaded with —import .

-v , —version #

Print node’s version.

Environment variables #

FORCE_COLOR=[1, 2, 3] #

The FORCE_COLOR environment variable is used to enable ANSI colorized output. The value may be:

  • 1 , true , or the empty string » indicate 16-color support,
  • 2 to indicate 256-color support, or
  • 3 to indicate 16 million-color support.

When FORCE_COLOR is 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.

NODE_DEBUG=module[,…] #

‘,’ -separated list of core modules that should print debug information.

NODE_DEBUG_NATIVE=module[,…] #

‘,’ -separated list of core C++ modules that should print debug information.

NODE_DISABLE_COLORS=1 #

When set, colors will not be used in the REPL.

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. A message will be emitted (once) with process.emitWarning() if the file is missing or malformed, but any errors are otherwise ignored.

Neither the well known nor extra certificates are used when the ca options property is explicitly specified for a TLS or HTTPS client or server.

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

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.

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=1 #

When set to 1 , process warnings are silenced.

NODE_OPTIONS=options. #

A space-separated list of command-line options. options. are interpreted before command-line options, so command-line options will override or compound after anything in options. . Node.js will exit with an error if an option that is not allowed in the environment is used, such as -p or a script file.

If an option value contains a space, it can be escaped using double quotes:

A singleton flag passed as a command-line option will override the same flag passed into NODE_OPTIONS :

A flag that can be passed multiple times will be treated as if its NODE_OPTIONS instances were passed first, and then its command-line instances afterwards:

Node.js options that are allowed are:

  • —conditions , -C
  • —diagnostic-dir
  • —disable-proto
  • —dns-result-order
  • —enable-fips
  • —enable-network-family-autoselection
  • —enable-source-maps
  • —experimental-abortcontroller
  • —experimental-import-meta-resolve
  • —experimental-json-modules
  • —experimental-loader
  • —experimental-modules
  • —experimental-network-imports
  • —experimental-policy
  • —experimental-shadow-realm
  • —experimental-specifier-resolution
  • —experimental-top-level-await
  • —experimental-vm-modules
  • —experimental-wasi-unstable-preview1
  • —experimental-wasm-modules
  • —force-context-aware
  • —force-fips
  • —force-node-api-uncaught-exceptions-policy
  • —frozen-intrinsics
  • —heapsnapshot-near-heap-limit
  • —heapsnapshot-signal
  • —http-parser
  • —icu-data-dir
  • —import
  • —input-type
  • —insecure-http-parser
  • —inspect-brk
  • —inspect-port , —debug-port
  • —inspect-publish-uid
  • —inspect
  • —max-http-header-size
  • —napi-modules
  • —no-addons
  • —no-deprecation
  • —no-experimental-fetch
  • —no-experimental-global-customevent
  • —no-experimental-global-webcrypto
  • —no-experimental-repl-await
  • —no-extra-info-on-fatal-exception
  • —no-force-async-hooks-checks
  • —no-global-search-paths
  • —no-warnings
  • —node-memory-debug
  • —openssl-config
  • —openssl-legacy-provider
  • —openssl-shared-config
  • —pending-deprecation
  • —policy-integrity
  • —preserve-symlinks-main
  • —preserve-symlinks
  • —prof-process
  • —redirect-warnings
  • —report-compact
  • —report-dir , —report-directory
  • —report-filename
  • —report-on-fatalerror
  • —report-on-signal
  • —report-signal
  • —report-uncaught-exception
  • —require , -r
  • —secure-heap-min
  • —secure-heap
  • —snapshot-blob
  • —test-only
  • —throw-deprecation
  • —title
  • —tls-cipher-list
  • —tls-keylog
  • —tls-max-v1.2
  • —tls-max-v1.3
  • —tls-min-v1.0
  • —tls-min-v1.1
  • —tls-min-v1.2
  • —tls-min-v1.3
  • —trace-atomics-wait
  • —trace-deprecation
  • —trace-event-categories
  • —trace-event-file-pattern
  • —trace-events-enabled
  • —trace-exit
  • —trace-sigint
  • —trace-sync-io
  • —trace-tls
  • —trace-uncaught
  • —trace-warnings
  • —track-heap-objects
  • —unhandled-rejections
  • —use-bundled-ca
  • —use-largepages
  • —use-openssl-ca
  • —v8-pool-size
  • —watch-path
  • —watch-preserve-output
  • —watch
  • —zero-fill-buffers

V8 options that are allowed are:

  • —abort-on-uncaught-exception
  • —disallow-code-generation-from-strings
  • —enable-etw-stack-walking
  • —huge-max-old-generation-size
  • —interpreted-frames-native-stack
  • —jitless
  • —max-old-space-size
  • —max-semi-space-size
  • —perf-basic-prof-only-functions
  • —perf-basic-prof
  • —perf-prof-unwinding-info
  • —perf-prof
  • —stack-trace-limit

—perf-basic-prof-only-functions , —perf-basic-prof , —perf-prof-unwinding-info , and —perf-prof are only available on Linux.

—enable-etw-stack-walking is only available on Windows.

NODE_PATH=path[:…] #

‘:’ -separated list of directories prefixed to the module search path.

On Windows, this is a ‘;’ -separated list instead.

NODE_PENDING_DEPRECATION=1 #

When set to 1 , emit pending deprecation warnings.

Pending deprecations are generally identical to a runtime deprecation with the notable exception that they are turned off by default and will not be emitted unless either the —pending-deprecation command-line flag, or the NODE_PENDING_DEPRECATION=1 environment variable, is set. Pending deprecations are used to provide a kind of selective «early warning» mechanism that developers may leverage to detect deprecated API usage.

NODE_PENDING_PIPE_INSTANCES=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=1 #

When set to 1 , instructs the module loader to preserve symbolic links when resolving and caching modules.

NODE_REDIRECT_WARNINGS=file #

When set, process warnings will be emitted to the given file instead of printing to stderr. The file will be created if it does not exist, and will be appended to if it does. If an error occurs while attempting to write the warning to the file, the warning will be written to stderr instead. This is equivalent to using the —redirect-warnings=file command-line flag.

NODE_REPL_HISTORY=file #

Path to the file used to store the persistent REPL history. The default path is

/.node_repl_history , which is overridden by this variable. Setting the value to an empty string ( » or ‘ ‘ ) disables persistent REPL history.

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.

NODE_SKIP_PLATFORM_CHECK=value #

If value equals ‘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.

NODE_TLS_REJECT_UNAUTHORIZED=value #

If value equals ‘0’ , certificate validation is disabled for TLS connections. This makes TLS, and HTTPS by extension, insecure. The use of this environment variable is strongly discouraged.

NODE_V8_COVERAGE=dir #

When set, Node.js will begin outputting V8 JavaScript code coverage and Source Map data to the directory provided as an argument (coverage information is written as JSON to files with a coverage prefix).

NODE_V8_COVERAGE will automatically propagate to subprocesses, making it easier to instrument applications that call the child_process.spawn() family of functions. NODE_V8_COVERAGE can be set to an empty string, to prevent propagation.

Coverage output #

Coverage is output as an array of ScriptCoverage objects on the top-level key result :

Source map cache #

If found, source map data is appended to the top-level key source-map-cache on the JSON coverage object.

source-map-cache is an object with keys representing the files source maps were extracted from, and values which include the raw source-map URL (in the key url ), the parsed Source Map v3 information (in the key data ), and the line lengths of the source file (in the key lineLengths ).

NO_COLOR=<any> #

NO_COLOR is an alias for NODE_DISABLE_COLORS . The value of the environment variable is arbitrary.

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, the environment variable is ignored.

SSL_CERT_DIR=dir #

If —use-openssl-ca is enabled, this overrides and sets OpenSSL’s directory containing trusted certificates.

Be aware that unless the child environment is explicitly set, this environment variable will be inherited by any child processes, and if they use OpenSSL, it may cause them to trust the same CAs as node.

SSL_CERT_FILE=file #

If —use-openssl-ca is enabled, this overrides and sets OpenSSL’s file containing trusted certificates.

Be aware that unless the child environment is explicitly set, this environment variable will be inherited by any child processes, and if they use OpenSSL, it may cause them to trust the same CAs as node.

Changing the TZ variable using process.env.TZ = changes the timezone on Windows as well.

Changing the TZ variable using process.env.TZ = changes the timezone on POSIX systems.

The TZ environment variable is used to specify the timezone configuration.

While Node.js does not support all of the various ways that TZ is handled in other environments, it does support basic timezone IDs (such as ‘Etc/UTC’ , ‘Europe/Paris’ , or ‘America/New_York’ ). It may support a few other abbreviations or aliases, but these are strongly discouraged and not guaranteed.

UV_THREADPOOL_SIZE=size #

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 do not exist, libuv’s threadpool is used to create asynchronous node APIs based on synchronous system APIs. Node.js APIs that use the threadpool are:

  • all fs APIs, other than the file watcher APIs and those that are explicitly synchronous
  • asynchronous crypto APIs such as crypto.pbkdf2() , crypto.scrypt() , crypto.randomBytes() , crypto.randomFill() , crypto.generateKeyPair()
  • dns.lookup()
  • all zlib APIs, other than those that are explicitly synchronous

Because libuv’s threadpool has a fixed size, it means that if for whatever reason any of these APIs takes a long time, other (seemingly unrelated) APIs that run in libuv’s threadpool will experience degraded performance. In order to mitigate this issue, one potential solution is to increase the size of libuv’s threadpool by setting the ‘UV_THREADPOOL_SIZE’ environment variable to a value greater than 4 (its current default value). For more information, see the libuv threadpool documentation.

Useful V8 options #

V8 has its own set of CLI options. Any V8 CLI option that is provided to node will be passed on to V8 to handle. V8’s options have no stability guarantee. The V8 team themselves don’t consider them to be part of their formal API, and reserve the right to change them at any time. Likewise, they are not covered by the Node.js stability guarantees. Many of the V8 options are of interest only to V8 developers. Despite this, there is a small set of V8 options that are widely applicable to Node.js, and they are documented here:

—max-old-space-size=SIZE (in megabytes) #

Sets the max memory size of V8’s old memory section. As memory consumption approaches the limit, V8 will spend more time on garbage collection in an effort to free unused memory.

On a machine with 2 GiB of memory, consider setting this to 1536 (1.5 GiB) to leave some memory for other uses and avoid swapping.

—max-semi-space-size=SIZE (in megabytes) #

Sets the maximum semi-space size for V8’s scavenge garbage collector in MiB (megabytes). Increasing the max size of a semi-space may improve throughput for Node.js at the cost of more memory consumption.

Since the young generation size of the V8 heap is three times (see YoungGenerationSizeFromSemiSpaceSize in V8) the size of the semi-space, an increase of 1 MiB to semi-space applies to each of the three individual semi-spaces and causes the heap size to increase by 3 MiB. The throughput improvement depends on your workload (see #42511).

The default value is 16 MiB for 64-bit systems and 8 MiB for 32-bit systems. To get the best configuration for your application, you should try different max-semi-space-size values when running benchmarks for your application.

Node.js version on the command line? (not the REPL)

I want to get the version of Node.js on the command line. I’m expecting to run a command like:

but that doesn’t work. Does anybody know what the command line would be? (i.e. not the REPL)

Penny Liu's user avatar

9 Answers 9

The command line for that is:

If node -v doesn’t work, but nodejs -v does, then something’s not set up quite right on your system. See this other question for ways to fix it.

If you’re referring to the shell command line, either of the following will work:

Just typing node version will cause node.js to attempt loading a module named version, which doesn’t exist unless you like working with confusing module names.

Try nodejs instead of just node

Srilu's user avatar

Just type npm version in your command line and it will display all the version details about node, npm, v8 engine etc.

How to Check Node Version? [Check Node JS Version]

Are looking to install the latest node js version to have better productivity, This article will guide you on how to check node version and how to install node on various OS.

List of content you will read in this article:

  • 1. What is Node.js?
  • 2. How to Check Node Version? [Check Node.js Vesion]
  • 3. Benefits of Node.js
  • 4. Drawbacks of Node.js
  • 5. Conclusion

Node.js is a widely adopted platform built on JavaScript runtime, allowing you to efficiently create scalable and web-based interactive applications. Node.js works on an event-driven and non-blocking I/O architecture, making it lightweight and perfect for creating data-intensive, real-time applications running on distributed systems. This article will give you a complete brief and step-by-step guide through which you can find how to check Node version [get Node version], i.e. that can be installed on different platforms. Let’s get started!

What is Node.js?

Node.js was developed as a server-side platform by Ryan Dahl in 2009. It’s only been 12 years and has gained popularity within no time. This software is designed to help create web-based servers and networking tools with JavaScript and various modules. It is capable of handling numerous core functionalities. It offers multiple modules that help in reducing the complications while writing the server applications using its APIs. Node.js is compatible with macOS, Windows, and Linux systems.

It has been significantly less time since this software has managed to attract large enterprises. Some major companies that rely on Node.js are Groupon, Netflix, IBM, Voxer, SAP, etc.

How to Check Node Version? [Check Node.js Vesion]

Node.js is a cross-platform software that can be installed on various platforms. Over time, it has multiple versions with advanced tools and technology. You can install and check Nodejs version on Linux, macOS, and Windows operating systems.

Here you will learn how to check node version installed in your operating system, along with the installation guide for Linux, Windows, and macOS.

How to check node.js version on Linux with the installation guide?

We are considering Ubuntu as a Linux distro here. You can easily find Node.js within Ubuntu’s repository and use commands for installation. Follow the below-mentioned steps to check the node version on Linux VPS too:

Step 1: Press ctrl+alt+t to open the terminal on your system and run this node command to install Node.js.

sudo apt install nodejs

Step 2: After installing the Node.js, check node version that you have installed with the help of the following node version command.

node -v or node –version

Step 3: It is strictly recommended that you install the Node package manager with Node.js. Npm offers you the open-source library of the Node.js packages. For installing NPM, use these commands.

sudo apt install npm
npm -v or npm –version

How to check Node version on windows with the installation guide?

To install Node.js on your Windows system, you need administrative rights on your user account and command line. Follow the below-mentioned steps if you want to install and check Node.js’ version of Node.js in Windows.

Step 1: Navigate to the official download site of Node.js and select the Windows installer button. It will start the download for the latest version by default. The NPM installer comes with an NPM package manager.

Step 2: After the completion of the download process, launch the installer. Open the directory where you store your download files.

Step 3: You will be asked if you want to run the software to confirm and click Run.

Step 4: You will be entered in the Node.js setup wizard and click on Next.

Step 5: You will be asked to accept the license, click Next after agreeing on the terms and conditions, and start installing the software.

Step 6: You will be asked for the software’s location, and you can leave the default location or fill in the required path and click Next.

Step 7: Next, select the components you want and do not wish to include accordingly and click Next.

Step 8: At last, you can click on the Install option to run the installer and click on Finish.

Run the following command on the command prompt, and you can verify the installed version of Node.js.

How to check node.js version on Mac and the installation guide?

You can go through the following steps for installing Node.js on macOS.

Step 1: Go to the official download page for Node.js and select macOS.

Step 2: Start running the download Node.js .pkg installer.

Step 3: Once the download process is complete, you can start running the installer, accepting all the details, and clicking installs to finish the procedure.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *