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

fix(deps): update node.js to v22 #93

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 Sep 14, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines major 20.x -> 22.12.0 age adoption passing confidence
node (source) engines minor 22.x -> 22.12.0 age adoption passing confidence
node (source) major 20.11.0 -> 22.12.0 age adoption passing confidence
@types/node (source) devDependencies minor ^22.9.1 -> ^22.10.2 age adoption passing confidence
@types/node (source) dependencies minor ^22.9.1 -> ^22.10.2 age adoption passing confidence

Release Notes

nodejs/node (node)

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 - "every weekend" (UTC), 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 changed the title chore(deps): update dependency @types/node to ^22.5.5 chore(deps): update dependency @types/node to ^22.5.5 - autoclosed Sep 20, 2024
@renovate renovate bot closed this Sep 20, 2024
@renovate renovate bot deleted the renovate/node-22.x branch September 20, 2024 19:43
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.5.5 - autoclosed chore(deps): update dependency @types/node to ^22.5.5 Sep 23, 2024
@renovate renovate bot reopened this Sep 23, 2024
@renovate renovate bot restored the renovate/node-22.x branch September 23, 2024 20:27
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.5.5 chore(deps): update dependency @types/node to ^22.6.1 Sep 23, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 74b4a93 to 30a9536 Compare September 25, 2024 04:33
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.6.1 chore(deps): update dependency @types/node to ^22.7.0 Sep 25, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.0 chore(deps): update dependency @types/node to ^22.7.1 Sep 25, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 30a9536 to 009229f Compare September 25, 2024 18:26
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.1 chore(deps): update dependency @types/node to ^22.7.2 Sep 25, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from a41f2bc to 1906a7d Compare September 26, 2024 18:42
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.2 chore(deps): update dependency @types/node to ^22.7.3 Sep 26, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.3 chore(deps): update dependency @types/node to ^22.7.4 Sep 27, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1906a7d to 1017003 Compare September 27, 2024 19:02
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.4 chore(deps): update dependency @types/node to ^22.7.4 - autoclosed Oct 2, 2024
@renovate renovate bot closed this Oct 2, 2024
@renovate renovate bot deleted the renovate/node-22.x branch October 2, 2024 10:37
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.4 - autoclosed chore(deps): update dependency @types/node to ^22.7.4 Oct 8, 2024
@renovate renovate bot restored the renovate/node-22.x branch October 8, 2024 01:37
@renovate renovate bot reopened this Oct 8, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1017003 to fe585e2 Compare October 8, 2024 03:51
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.4 chore(deps): update dependency @types/node to ^22.7.5 Oct 8, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from fe585e2 to ba0fc66 Compare October 17, 2024 01:00
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.5 chore(deps): update dependency @types/node to ^22.7.6 Oct 17, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ba0fc66 to 71ba262 Compare October 19, 2024 05:10
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.6 chore(deps): update dependency @types/node to ^22.7.7 Oct 19, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 6a222a2 to 819f1b1 Compare October 23, 2024 04:08
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.7.9 chore(deps): update dependency @types/node to ^22.8.0 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 819f1b1 to f452fde Compare October 25, 2024 13:24
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.8.0 chore(deps): update dependency @types/node to ^22.8.1 Oct 26, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from f452fde to 86ba960 Compare October 26, 2024 01:06
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.8.1 chore(deps): update dependency @types/node to ^22.8.2 Oct 28, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 18f5c01 to a96e553 Compare October 29, 2024 14:15
@renovate renovate bot changed the title chore(deps): update dependency @types/node to ^22.8.2 chore(deps): update node.js to v22 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 6 times, most recently from 2947a0d to ff6edcd Compare November 5, 2024 03:54
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 201f84e to ea4f219 Compare November 20, 2024 14:58
@renovate renovate bot changed the title chore(deps): update node.js to v22 chore(deps): update node.js to v22.11.0 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ea4f219 to 46b9afc Compare November 23, 2024 00:13
@renovate renovate bot changed the title chore(deps): update node.js to v22.11.0 chore(deps): update node.js to v22 Nov 23, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from c6d5fbf to 7219ac6 Compare November 28, 2024 06:58
@renovate renovate bot force-pushed the renovate/node-22.x branch from 7219ac6 to 46f82db Compare December 3, 2024 22:38
@renovate renovate bot changed the title chore(deps): update node.js to v22 chore(deps): update node.js to v22.12.0 Dec 8, 2024
@renovate renovate bot changed the title chore(deps): update node.js to v22.12.0 chore(deps): update node.js to v22 Dec 8, 2024
@renovate renovate bot changed the title chore(deps): update node.js to v22 fix(deps): update node.js to v22 Dec 10, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 46f82db to 6c40461 Compare December 11, 2024 10:30
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