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.

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

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

Open
wants to merge 1 commit into
base: chore/renovateBaseBranch
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 20.18.1 -> 22.11.0 age adoption passing confidence
@types/node (source) devDependencies major 20.17.7 -> 22.9.3 age adoption passing confidence
node final major 20.18.1-bullseye -> 22.11.0-bullseye age adoption passing confidence
node stage major 20.18.1-bullseye -> 22.11.0-bullseye age adoption passing confidence

Release Notes

nodejs/node (node)

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 - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, 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.

@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from db363ce to b54cb98 Compare May 17, 2024 16:59
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 4a7004b to 8bbaa05 Compare July 5, 2024 17:10
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from da24265 to aeaac22 Compare July 13, 2024 23:23
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from acee444 to 7afb459 Compare July 19, 2024 19:12
@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from 4ae4aa7 to c23befd Compare August 3, 2024 21:27
@renovate renovate bot changed the title chore(deps): update node.js to v22 chore(deps): update node docker tag to v22 Aug 9, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 711adb9 to 1c83e49 Compare August 16, 2024 18:47
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 32bb525 to f822cf0 Compare August 24, 2024 18:57
@renovate renovate bot changed the title chore(deps): update node docker tag to v22 chore(deps): update node.js to v22 Aug 30, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from 0cf586b to a347a0c Compare September 6, 2024 16:04
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from b406b9f to 0748f03 Compare September 14, 2024 03:21
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from e19c5e7 to 2c4acef Compare September 27, 2024 15:40
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 31a5e09 to 6b24ce4 Compare September 29, 2024 00:38
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 1df8717 to b88d071 Compare October 12, 2024 22:06
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from 537d4c4 to ddd69d1 Compare October 19, 2024 08:06
@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from 1eb274a to c9a3fc1 Compare October 27, 2024 00:32
@renovate renovate bot changed the title chore(deps): update node.js to v22 chore(deps): update dependency node to v22 Nov 1, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from 5dab245 to 7d345b3 Compare November 8, 2024 18:28
@renovate renovate bot changed the title chore(deps): update dependency node to v22 chore(deps): update node.js to v22 Nov 15, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from cd41445 to 1bd9ba5 Compare November 23, 2024 06:50
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