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.12.0 #74

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 2, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor v22.0.0 -> 22.12.0 age adoption passing confidence
node (source) engines major >=18.0.0 -> >=22.12.0 age adoption passing confidence
@types/node (source) devDependencies major ^20.12.7 -> ^22.10.5 age adoption passing confidence
node (source) minor 22.0.0 -> 22.12.0 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: Enabled.

Rebasing: Whenever PR is behind base branch, 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

github-actions bot commented May 2, 2024

size-limit report 📦

Path Size
-16 B (0%)
dist/index.umd.js 362 B (0%)
dist/index.modern.mjs 265 B (0%)

@renovate renovate bot force-pushed the renovate/node-22.x branch from cb96035 to 8f76119 Compare May 12, 2024 12:06
@renovate renovate bot force-pushed the renovate/node-22.x branch from 8f76119 to ee77a26 Compare May 23, 2024 02:54
@renovate renovate bot changed the title chore(deps): update dependency node to v22.1.0 chore(deps): update dependency node to v22.2.0 May 23, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ee77a26 to 505cb4c Compare June 15, 2024 06:00
@renovate renovate bot changed the title chore(deps): update dependency node to v22.2.0 chore(deps): update dependency node to v22.3.0 Jun 15, 2024
@renovate renovate bot changed the title chore(deps): update dependency node to v22.3.0 chore(deps): update dependency node to v22.4.0 Jul 3, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from fd00d8d to ad7dafd Compare July 8, 2024 23:32
@renovate renovate bot changed the title chore(deps): update dependency node to v22.4.0 chore(deps): update dependency node to v22.4.1 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ad7dafd to c7aa904 Compare July 17, 2024 20:57
@renovate renovate bot changed the title chore(deps): update dependency node to v22.4.1 chore(deps): update dependency node to v22.5.0 Jul 17, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from c7aa904 to dff61c0 Compare July 19, 2024 23:42
@renovate renovate bot changed the title chore(deps): update dependency node to v22.5.0 chore(deps): update dependency node to v22.5.1 Jul 19, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from dff61c0 to 2019a51 Compare August 10, 2024 05:57
@renovate renovate bot changed the title chore(deps): update dependency node to v22.5.1 chore(deps): update dependency node to v22.6.0 Aug 10, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 2019a51 to ce07bee Compare August 24, 2024 11:45
@renovate renovate bot changed the title chore(deps): update dependency node to v22.6.0 chore(deps): update dependency node to v22.7.0 Aug 24, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ce07bee to 9715a86 Compare September 6, 2024 05:49
@renovate renovate bot changed the title chore(deps): update dependency node to v22.7.0 chore(deps): update dependency node to v22.8.0 Sep 6, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 9715a86 to 15b5403 Compare September 18, 2024 05:34
@renovate renovate bot changed the title chore(deps): update dependency node to v22.8.0 chore(deps): update dependency node to v22.9.0 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 15b5403 to 065002e Compare October 18, 2024 05:53
@renovate renovate bot changed the title chore(deps): update dependency node to v22.9.0 chore(deps): update dependency node to v22.10.0 Oct 18, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 065002e to b6dd0ef Compare October 30, 2024 08:52
@renovate renovate bot changed the title chore(deps): update dependency node to v22.10.0 chore(deps): update dependency node to v22.11.0 Oct 30, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from fe063b3 to e7f5213 Compare November 5, 2024 02:57
@renovate renovate bot changed the title chore(deps): update dependency node to v22.11.0 chore(deps): update node.js to v22.11.0 Nov 14, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 3 times, most recently from 9b8c5a7 to c388e7b Compare November 26, 2024 21:02
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 3205250 to 30f7ea1 Compare December 4, 2024 08:53
@renovate renovate bot changed the title chore(deps): update node.js to v22.11.0 chore(deps): update node.js to v22.12.0 Dec 4, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 30f7ea1 to 0b8a0a6 Compare December 11, 2024 17:02
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from e97f5d4 to 327822d Compare January 3, 2025 02:37
@renovate renovate bot force-pushed the renovate/node-22.x branch from 327822d to 6714c8f Compare January 4, 2025 02: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