Skip to content
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.

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

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 29, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 20 -> 22 age adoption passing confidence
node (source) engines major 20.x.x -> 22.x age adoption passing confidence
@types/node (source) devDependencies major 20.17.9 -> 22.13.1 age adoption passing confidence

Release Notes

nodejs/node (node)

v22.13.1

Compare Source

v22.13.0

Compare Source

v22.12.0

Compare Source

v22.11.0

Compare Source

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

Contributed by Joyee Cheung in #​54648.

node --run is now stable

This CLI flag runs a specified command from a package.json's "scripts" object.

For the following package.json:

{
  "scripts": {
    "test": "node --test-reporter junit --test ./test"
  }
}

You can run node --run test and that would start the test suite.

Contributed by Yagiz Nizipli in #​53763.

Other notable changes
  • [f0b441230a] - (SEMVER-MINOR) crypto: add KeyObject.prototype.toCryptoKey (Filip Skokan) #​55262
  • [349d2ed07b] - (SEMVER-MINOR) crypto: add Date fields for validTo and validFrom (Andrew Moon) #​54159
  • [bebc95ed58] - doc: add abmusse to collaborators (Abdirahim Musse) #​55086
  • [914db60159] - (SEMVER-MINOR) http2: expose nghttp2_option_set_stream_reset_rate_limit as an option (Maël Nison) #​54875
  • [f7c3b03759] - (SEMVER-MINOR) lib: propagate aborted state to dependent signals before firing events (jazelly) #​54826
  • [32261fc98a] - (SEMVER-MINOR) module: support loading entrypoint as url (RedYetiDev) #​54933
  • [06957ff355] - (SEMVER-MINOR) module: implement flushCompileCache() (Joyee Cheung) #​54971
  • [2dcf70c347] - (SEMVER-MINOR) module: throw when invalid argument is passed to enableCompileCache() (Joyee Cheung) #​54971
  • [f9b19d7c44] - (SEMVER-MINOR) module: write compile cache to temporary file and then rename it (Joyee Cheung) #​54971
  • [e95163b170] - (SEMVER-MINOR) process: add process.features.require_module (Joyee Cheung) #​55241
  • [4050f68e5d] - (SEMVER-MINOR) process: add process.features.typescript (Aviv Keller) #​54295
  • [86f7cb802d] - (SEMVER-MINOR) test_runner: support custom arguments in run() (Aviv Keller) #​55126
  • [b62f2f8259] - (SEMVER-MINOR) test_runner: add 'test:summary' event (Colin Ihrig) #​54851
  • [d7c708aec5] - (SEMVER-MINOR) test_runner: add support for coverage via run() (Chemi Atlow) #​53937
  • [5fda4a1498] - (SEMVER-MINOR) worker: add markAsUncloneable api (Jason Zhang) #​55234
Commits

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 these updates again.


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

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

Copy link

vercel bot commented Oct 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
isitfriday ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 4, 2025 0:36am

@renovate renovate bot force-pushed the renovate/node-22.x branch from 9ae5a80 to b47035f Compare October 29, 2024 15:24
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v22 chore(deps): update dependency node to v22 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from b47035f to d3269cf Compare October 29, 2024 19:15
@renovate renovate bot force-pushed the renovate/node-22.x branch from d3269cf to 39cab3a Compare October 30, 2024 03:10
@renovate renovate bot force-pushed the renovate/node-22.x branch from 39cab3a to b3012fd Compare October 30, 2024 09:14
@renovate renovate bot force-pushed the renovate/node-22.x branch from b3012fd to 874b382 Compare October 31, 2024 08:34
@renovate renovate bot force-pushed the renovate/node-22.x branch from 874b382 to 8e10b27 Compare October 31, 2024 13:29
@renovate renovate bot force-pushed the renovate/node-22.x branch from 8e10b27 to d45202a Compare October 31, 2024 20:42
@renovate renovate bot force-pushed the renovate/node-22.x branch from d45202a to 2a91ce7 Compare November 1, 2024 02:03
@renovate renovate bot force-pushed the renovate/node-22.x branch from 2a91ce7 to b56d8ac Compare November 3, 2024 07:04
@renovate renovate bot force-pushed the renovate/node-22.x branch from b56d8ac to 4cb6f2c Compare November 3, 2024 13:59
@renovate renovate bot force-pushed the renovate/node-22.x branch from 4cb6f2c to 2219b80 Compare November 5, 2024 04: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 from 2219b80 to f630d92 Compare November 19, 2024 19:37
@renovate renovate bot force-pushed the renovate/node-22.x branch from f630d92 to 9ffa55d Compare November 23, 2024 02:17
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1b2f7f3 to 1f8b16b Compare November 28, 2024 13:28
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1f8b16b to 1304c4a Compare December 5, 2024 00:49
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1304c4a to 8af7f1d Compare December 11, 2024 12:34
@renovate renovate bot force-pushed the renovate/node-22.x branch from 8af7f1d to 724bf00 Compare January 1, 2025 02:29
@renovate renovate bot force-pushed the renovate/node-22.x branch from 724bf00 to a94d2bf Compare January 2, 2025 21:23
@renovate renovate bot force-pushed the renovate/node-22.x branch from a94d2bf to 24c8c4c Compare January 3, 2025 10:31
@renovate renovate bot force-pushed the renovate/node-22.x branch from 24c8c4c to ebe6c26 Compare January 13, 2025 21:34
@renovate renovate bot force-pushed the renovate/node-22.x branch from ebe6c26 to 7088c6f Compare January 16, 2025 01:35
@renovate renovate bot force-pushed the renovate/node-22.x branch from 7088c6f to 45d0c12 Compare January 23, 2025 06:03
@renovate renovate bot force-pushed the renovate/node-22.x branch from 45d0c12 to d622b7d Compare January 23, 2025 10:18
@renovate renovate bot force-pushed the renovate/node-22.x branch from d622b7d to bef0a68 Compare January 23, 2025 23:14
@renovate renovate bot force-pushed the renovate/node-22.x branch from bef0a68 to 4c74e55 Compare January 28, 2025 05:32
@renovate renovate bot force-pushed the renovate/node-22.x branch from 4c74e55 to eca34bc Compare February 1, 2025 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants