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 #236

Merged
merged 1 commit into from
Dec 18, 2024
Merged

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

merged 1 commit into from
Dec 18, 2024

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.18.1 -> 22.12.0 age adoption passing confidence
@types/node (source) dependencies major 20.17.10 -> 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 - 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.

@renovate renovate bot added the dependencies Change in project dependencies. label Oct 29, 2024
@renovate renovate bot assigned rainx Oct 29, 2024
@renovate renovate bot requested a review from rainx October 29, 2024 01:18
@rainx rainx force-pushed the renovate/node-22.x branch from 296029b to f04021f Compare October 29, 2024 01:19
@renovate renovate bot force-pushed the renovate/node-22.x branch from f04021f to b867e7d Compare October 29, 2024 15:49
@renovate renovate bot changed the title fix(deps): update dependency @types/node to v22 chore(deps): update dependency node to v22 Oct 29, 2024
@rainx rainx force-pushed the renovate/node-22.x branch from b867e7d to 3829a59 Compare October 29, 2024 15:50
@renovate renovate bot force-pushed the renovate/node-22.x branch from 3829a59 to eaa90b9 Compare October 29, 2024 20:15
@rainx rainx force-pushed the renovate/node-22.x branch from eaa90b9 to 1618ad2 Compare October 29, 2024 20:16
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1618ad2 to 56a443d Compare October 31, 2024 06:19
@rainx rainx force-pushed the renovate/node-22.x branch from 56a443d to 807d6e1 Compare October 31, 2024 06:20
@renovate renovate bot force-pushed the renovate/node-22.x branch from 807d6e1 to 525834d Compare October 31, 2024 20:03
@rainx rainx force-pushed the renovate/node-22.x branch from 525834d to 3f80311 Compare October 31, 2024 20:04
@renovate renovate bot force-pushed the renovate/node-22.x branch from 3f80311 to fb6f93e Compare November 1, 2024 07:56
@rainx rainx force-pushed the renovate/node-22.x branch from fb6f93e to 0d172b5 Compare November 1, 2024 07:57
@renovate renovate bot force-pushed the renovate/node-22.x branch from 0d172b5 to dd93b76 Compare November 1, 2024 09:52
@rainx rainx force-pushed the renovate/node-22.x branch from dd93b76 to bf0dff6 Compare November 1, 2024 09:53
@renovate renovate bot force-pushed the renovate/node-22.x branch from bf0dff6 to 2713591 Compare November 3, 2024 09:07
@rainx rainx force-pushed the renovate/node-22.x branch from 2713591 to 9991879 Compare November 3, 2024 09:08
@renovate renovate bot force-pushed the renovate/node-22.x branch from 9991879 to 5b7eb54 Compare November 3, 2024 09:15
@rainx rainx force-pushed the renovate/node-22.x branch from 5b7eb54 to e736088 Compare November 3, 2024 09:16
@renovate renovate bot force-pushed the renovate/node-22.x branch from e736088 to f82dfc3 Compare November 4, 2024 04:17
@rainx rainx force-pushed the renovate/node-22.x branch from f82dfc3 to 999b918 Compare November 4, 2024 04:18
@renovate renovate bot force-pushed the renovate/node-22.x branch from 999b918 to 4b02073 Compare November 5, 2024 04:58
@rainx rainx force-pushed the renovate/node-22.x branch from 4b02073 to e503a43 Compare November 5, 2024 04:59
@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 e503a43 to 803a3f4 Compare November 18, 2024 04:58
@rainx rainx force-pushed the renovate/node-22.x branch from 803a3f4 to 8b0ff67 Compare November 18, 2024 04:58
@renovate renovate bot force-pushed the renovate/node-22.x branch from 8b0ff67 to e920551 Compare November 19, 2024 19:13
@rainx rainx force-pushed the renovate/node-22.x branch from e920551 to 61100e1 Compare November 19, 2024 19:14
@renovate renovate bot force-pushed the renovate/node-22.x branch from c7f5eeb to ae671d0 Compare November 23, 2024 09:44
@rainx rainx force-pushed the renovate/node-22.x branch from ae671d0 to 6849580 Compare November 23, 2024 09:45
@renovate renovate bot force-pushed the renovate/node-22.x branch from 6849580 to e7a9ca9 Compare November 25, 2024 03:14
@rainx rainx force-pushed the renovate/node-22.x branch from e7a9ca9 to dd9384a Compare November 25, 2024 03:15
@renovate renovate bot force-pushed the renovate/node-22.x branch from dd9384a to 16d243b Compare November 25, 2024 23:50
@rainx rainx force-pushed the renovate/node-22.x branch from 16d243b to e41f051 Compare November 25, 2024 23:51
@renovate renovate bot force-pushed the renovate/node-22.x branch from e41f051 to 0637403 Compare November 26, 2024 00:44
@rainx rainx force-pushed the renovate/node-22.x branch from 0637403 to 85dad8c Compare November 26, 2024 00:44
@renovate renovate bot force-pushed the renovate/node-22.x branch from 85dad8c to 65a5815 Compare November 26, 2024 04:46
@rainx rainx force-pushed the renovate/node-22.x branch from 65a5815 to 04f3660 Compare November 26, 2024 04:47
@renovate renovate bot force-pushed the renovate/node-22.x branch from 04f3660 to 0dc15c5 Compare November 28, 2024 07:13
@rainx rainx force-pushed the renovate/node-22.x branch from 0dc15c5 to fb68ada Compare November 28, 2024 07:13
@renovate renovate bot force-pushed the renovate/node-22.x branch from fb68ada to 28aab4a Compare November 28, 2024 07:16
@rainx rainx force-pushed the renovate/node-22.x branch from 28aab4a to 2c66722 Compare November 28, 2024 07:17
@renovate renovate bot force-pushed the renovate/node-22.x branch from 2c66722 to 814ae5f Compare December 2, 2024 03:48
@rainx rainx force-pushed the renovate/node-22.x branch from 814ae5f to 8071f6f Compare December 2, 2024 03:48
@renovate renovate bot force-pushed the renovate/node-22.x branch from 8071f6f to 8cca815 Compare December 3, 2024 23:12
@rainx rainx force-pushed the renovate/node-22.x branch from 8cca815 to 02ce2e7 Compare December 3, 2024 23:12
@renovate renovate bot force-pushed the renovate/node-22.x branch from 02ce2e7 to 45c341e Compare December 9, 2024 03:17
@rainx rainx force-pushed the renovate/node-22.x branch from 45c341e to 8fd7a94 Compare December 9, 2024 03:18
@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 8fd7a94 to a56c36d Compare December 11, 2024 11:41
@rainx rainx force-pushed the renovate/node-22.x branch from a56c36d to 61a9f40 Compare December 11, 2024 11:42
@renovate renovate bot force-pushed the renovate/node-22.x branch from 61a9f40 to 993e863 Compare December 11, 2024 11:49
@rainx rainx force-pushed the renovate/node-22.x branch from 993e863 to 6727a18 Compare December 11, 2024 11:50
@renovate renovate bot force-pushed the renovate/node-22.x branch from 6727a18 to 865ad6d Compare December 16, 2024 03:18
@rainx rainx force-pushed the renovate/node-22.x branch from 865ad6d to 894e462 Compare December 16, 2024 03:18
@rainx rainx merged commit 2c0745b into main Dec 18, 2024
10 checks passed
@renovate renovate bot deleted the renovate/node-22.x branch December 18, 2024 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Change in project dependencies.
Development

Successfully merging this pull request may close these issues.

1 participant