Node.js 22.10.0 (32-bit)

What's new in this version:

Notable Changes:
New "module-sync" exports condition:
- This release introduces a "module-sync" exports condition that's enabled when require(esm) is enabled, so packages can supply a synchronous ES module to the Node.js module loader, no matter if it's being required or imported. This is similar to the "module" condition that bundlers have been using to support require(esm) in Node.js, and allows dual-package authors to opt into ESM-first only on newer versions of Node.js that supports require(esm) to avoid the dual-package hazard.
- For package authors: this only serves as a feature-detection mechanism for packages that wish to support both CJS and ESM users during the period when some active Node.js LTS versions support require(esm) while some older ones don't. When all active Node.js LTS lines support require(esm), packages can simplify their distributions by bumping the major version, dropping their CJS exports, and removing the module-sync exports condition (with only main or default targetting the ESM exports). If the package needs to support both bundlers and being run unbundled on Node.js during the transition period, use both module-sync and module and point them to the same ESM file. If the package already doesn't want to support older versions of Node.js that doesn't support require(esm), don't use this export condition.
- For bundlers/tools: they should avoid implementing this stop-gap condition. Most existing bundlers implement the de-facto bundler standard module exports condition, and that should be enough to support users who want to bundle ESM from CJS consumers. Users who want both bundlers and Node.js to recognize the ESM exports can use both module/module-sync conditions during the transition period, and can drop module-sync+module when they no longer need to support older versions of Node.js. If tools do want to support this condition, it's recommended to make the resolution rules in the graph pointed by this condition match the Node.js native ESM rules to avoid divergence.
- We ended up implementing a condition with a different name instead of reusing "module", because existing code in the ecosystem using the "module" condition sometimes also expect the module resolution for these ESM files to work in CJS style, which is supported by bundlers, but the native Node.js loader has intentionally made ESM resolution different from CJS resolution (e.g. forbidding import './noext' or import './directory'), so it would be breaking to implement a "module" condition without implementing the forbidden ESM resolution rules. For now, this just implements a new condition as semver-minor so it can be backported to older LTS.

Other notable changes:
- (SEMVER-MINOR) crypto: add KeyObject.prototype.toCryptoKey
- (SEMVER-MINOR) crypto: add Date fields for validTo and validFrom
- doc: add abmusse to collaborators
- (SEMVER-MINOR) http2: expose nghttp2_option_set_stream_reset_rate_limit as an option
- (SEMVER-MINOR) lib: propagate aborted state to dependent signals before firing events
- (SEMVER-MINOR) module: support loading entrypoint as url
- (SEMVER-MINOR) module: implement flushCompileCache()
- (SEMVER-MINOR) module: throw when invalid argument is passed to enableCompileCache()
- (SEMVER-MINOR) module: write compile cache to temporary file and then rename it
- (SEMVER-MINOR) process: add process.features.require_module
- (SEMVER-MINOR) process: add process.features.typescript
- (SEMVER-MINOR) test_runner: support custom arguments in run()
- (SEMVER-MINOR) test_runner: add 'test:summary' event
- (SEMVER-MINOR) test_runner: add support for coverage via run()
- (SEMVER-MINOR) worker: add markAsUncloneable api