Skip to content

chore(deps): update node.js to v22 #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update node.js to v22 #208

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 29, 2024 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
node final major 20.18.0-alpine3.19 → 22.12.0-alpine3.19

Release Notes

nodejs/node (node)

v22.12.0: 2024-12-03, Version 22.12.0 'Jod' (LTS), @​ruyadorno

Compare Source

Notable Changes
require(esm) is now enabled by default

Support for loading native ES modules using require() had been available on v20.x and v22.x under the command line flag --experimental-require-module, and available by default on v23.x. In this release, it is now no longer behind a flag on v22.x.

This feature is still experimental, and we are looking for user feedback to make more final tweaks before fully stabilizing it. For this reason, on v22.x, when the Node.js instance encounters a native ES module in require() for the first time, it will emit an experimental warning unless require() comes from a path that contains node_modules. If there happens to be any regressions caused by this feature, users can report it to the Node.js issue tracker. Meanwhile this feature can also be disabled using --no-experimental-require-module as a workaround.

With this feature enabled, Node.js will no longer throw ERR_REQUIRE_ESM if require() is used to load a ES module. It can, however, throw ERR_REQUIRE_ASYNC_MODULE if the ES module being loaded or its dependencies contain top-level await. When the ES module is loaded successfully by require(), the returned object will either be a ES module namespace object similar to what's returned by import(), or what gets exported as "module.exports" in the ES module.

Users can check process.features.require_module to see whether require(esm) is enabled in the current Node.js instance. For packages, the "module-sync" exports condition can be used as a way to detect require(esm) support in the current Node.js instance and allow both require() and import to load the same native ES module. See the documentation for more details about this feature.

Contributed by Joyee Cheung in #​55085

Added resizable ArrayBuffer support in Buffer

When a Buffer is created using a resizable ArrayBuffer, the Buffer length will now correctly change as the underlying ArrayBuffer size is changed.

const ab = new ArrayBuffer(10, { maxByteLength: 20 });
const buffer = Buffer.from(ab);
console.log(buffer.byteLength); 10
ab.resize(15);
console.log(buffer.byteLength); 15
ab.resize(5);
console.log(buffer.byteLength); 5

Contributed by James Snell in #​55377

Update root certificates to NSS 3.104

This is the version of NSS that shipped in Firefox 131.0 on 2024-10-01.

Certificates added:

  • FIRMAPROFESIONAL CA ROOT-A WEB
  • TWCA CYBER Root CA
  • SecureSign Root CA12
  • SecureSign Root CA14
  • SecureSign Root CA15

Contributed by Richard Lau in #​55681

Other Notable Changes
  • [4920869935] - (SEMVER-MINOR) assert: make assertion_error use Myers diff algorithm (Giovanni Bucci) #​54862
  • [ccffd3b819] - doc: enforce strict policy to semver-major releases (Rafael Gonzaga) #​55732
  • [acc6806900] - doc: add jazelly to collaborators (Jason Zhang) #​55531
  • [88d91e8bc2] - esm: mark import attributes and JSON module as stable (Nicolò Ribaudo) #​55333
  • [98bfc7dce5] - (SEMVER-MINOR) http: add diagnostic channel http.client.request.created (Marco Ippolito) #​55586
  • [337f61fb25] - (SEMVER-MINOR) lib: add UV_UDP_REUSEPORT for udp (theanarkh) #​55403
  • [1628c48ad6] - (SEMVER-MINOR) net: add UV_TCP_REUSEPORT for tcp (theanarkh) #​55408
  • [457e73f4c9] - (SEMVER-MINOR) sqlite: add support for SQLite Session Extension (Bart Louwers) #​54181
Commits

v22.11.0: 2024-10-29, Version 22.11.0 'Jod' (LTS), @​richardlau

Compare Source

Notable Changes

This release marks the transition of Node.js 22.x into Long Term Support (LTS)
with the codename 'Jod'. The 22.x release line now moves into "Active LTS"
and will remain so until October 2025. After that time, it will move into
"Maintenance" until end of life in April 2027.

Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 22.10.0 are included.

OpenSSL 3.x

Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the quictls OpenSSL fork).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.

v22.10.0: 2024-10-16, Version 22.10.0 (Current), @​aduh95

Compare Source

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.

{
  "type": "module",
  "exports": {
    "node": {
      // On new version of Node.js, both require() and import get
      // the ESM version
      "module-sync": "./index.js",
      // On older version of Node.js, where "module-sync" and require(esm) are
      // not supported, use the CJS version to avoid dual-package hazard.
      // When package authors think it's time to drop support for older versions of
      // Node.js, they can remove the exports conditions and just use "main": "index.js".
      "default": "./dist/index.cjs"
    },
    // On any other environment, use the ESM version.
    "default": "./index.js"
  }
}

Or if the package is only meant to be run on Node.js and wants to fallback to
CJS on older versions that don't have require(esm):

{
  "type": "module",
  "exports": {
    // On new version of Node.js, both require() and import get the ESM version
    "module-sync": "./index.js",
    // On older version of Node.js, where "module-sync" and require(esm) are
    // not supported, use the CJS version to avoid dual-package hazard.
    // When package authors think it's time to drop support for older versions of
    // Node.js, they can remove the exports conditions and just use "main": "index.js".
    "default": "./dist/index.cjs"
  }
}

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 s

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/node-22.x branch from dcd1fb2 to 90d55a3 Compare October 29, 2024 17:22
@renovate renovate bot changed the title chore(deps): update node.js to v22 chore(deps): update dependency node to v22 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from 628f496 to 7ee0129 Compare November 5, 2024 03:21
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 2b41ae9 to e5e3ef3 Compare November 13, 2024 01:27
@renovate renovate bot changed the title chore(deps): update dependency node to v22 chore(deps): update node.js to v22 Nov 13, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 705d9f7 to d2e273a Compare November 23, 2024 07:09
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from a669d89 to c082ab0 Compare November 28, 2024 07:05
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from d370444 to 7aae8cf Compare December 11, 2024 11:12
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from ca5bcf6 to 128f9d9 Compare January 3, 2025 07:41
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 5512720 to a92b284 Compare January 13, 2025 20:14
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from 42958af to ad11ae2 Compare January 23, 2025 04:25
@renovate renovate bot force-pushed the renovate/node-22.x branch from ad11ae2 to 89f20b1 Compare January 23, 2025 23:05
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from f31fd83 to e11c5d8 Compare July 15, 2025 07:35
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from a88cf00 to 105be31 Compare July 19, 2025 01:48
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from a9708d1 to 4a1822d Compare July 31, 2025 23:54
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 03b47cc to 3c814c4 Compare August 15, 2025 09:50
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 16103a0 to 94f2cd0 Compare August 31, 2025 09:27
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 1ae0720 to 9338311 Compare September 13, 2025 20:58
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from a5194ef to 918f636 Compare September 18, 2025 02:37
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from c7e4fe0 to 6f49c74 Compare October 1, 2025 01:54
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 0d4b807 to c638736 Compare October 11, 2025 17:46
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 9fe00aa to d51ece0 Compare October 21, 2025 02:09
@renovate renovate bot force-pushed the renovate/node-22.x branch from d51ece0 to abfb14b Compare October 28, 2025 01:36
@renovate renovate bot force-pushed the renovate/node-22.x branch from abfb14b to 99874ae Compare October 28, 2025 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants