Is a JavaScript runtime built on Chrome`s V8 JavaScript engine

Node.js 22.1.0 (32-bit)

May, 3rd 2024 - 24.41 MB - Open Source

Free Download

Security Status

Latest Version

Node.js 22.2.0 (32-bit)
Operating System

Windows 7 / Windows 8 / Windows 10 / Windows 11
User Rating

Click to vote
Author / Product

Node.js Foundation / External Link
Filename

node-v22.1.0-x86.msi
MD5 Checksum

17cf80f91995a0827e2f0383f42873a6

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of Node.js 22.1.0 (32-bit).

For those interested in downloading the most recent release of Node.js (32-bit) or reading our review, simply click here.

All old versions distributed on our website are completely virus-free and available for download at no cost.

We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

Download Node.js 22.1.0 (32-bit)

Node.js 22.1.0 (32-bit) Screenshots

The images below have been resized. Click on them to view the screenshots in full size.

What's new in this version:

- module: implement NODE_COMPILE_CACHE for automatic on-disk code caching
- This patch implements automatic on-disk code caching that can be enabled via an environment variable NODE_COMPILE_CACHE=/path/to/cache/dir.
- When set, whenever Node.js compiles a CommonJS or a ECMAScript Module, it will use on-disk V8 code cache persisted in the specified directory to speed up the compilation. This may slow down the first load of a module graph, but subsequent loads of the same module graph may get a significant speedup if the contents of the modules do not change. Locally, this speeds up loading of test/fixtures/snapshot/typescript.js from ~130ms to ~80ms.
- To clean up the generated code cache, simply remove the directory. It will be recreated the next time the same directory is used for NODE_COMPILE_CACHE.
- Compilation cache generated by one version of Node.js may not be used by a different version of Node.js. Cache generated by different versions of Node.js will be stored separately if the same directory is used to persist the cache, so they can co-exist.
- Caveat: currently when using this with V8 JavaScript code coverage, the coverage being collected by V8 may be less precise in functions that are deserialized from the code cache. It's recommended to turn this off when running tests to generate precise coverage.