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): bump node to 22.12.0 #1059

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 18.20.3 -> 22.12.0 age adoption passing confidence
@types/node (source) resolutions major 20.6.3 -> 22.10.2 age adoption passing confidence
@types/node (source) devDependencies major 20.6.3 -> 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 - "on monday before 6:00am" in timezone 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 added the dependencies Pull requests that update a dependency file label Jul 29, 2024
Copy link

changeset-bot bot commented Jul 29, 2024

⚠️ No Changeset found

Latest commit: 6da5bc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title chore(deps): bump @types/node to 22.0.0 chore(deps): bump @types/node to 22.0.1 Jul 31, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 72ce677 to d77d262 Compare July 31, 2024 19:22
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.0.1 chore(deps): bump @types/node to 22.0.2 Jul 31, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from e4a77b4 to ccd3f53 Compare August 3, 2024 00:29
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.0.2 chore(deps): bump @types/node to 22.1.0 Aug 3, 2024
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.1.0 chore(deps): bump @types/node to 22.2.0 Aug 9, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 467b761 to ba12609 Compare August 14, 2024 07:44
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.2.0 chore(deps): bump @types/node to 22.3.0 Aug 14, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from ba12609 to 1e0c3d1 Compare August 16, 2024 19:44
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.3.0 chore(deps): bump @types/node to 22.4.0 Aug 16, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1e0c3d1 to a9e36b1 Compare August 19, 2024 04:39
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.4.0 chore(deps): bump @types/node to 22.4.1 Aug 19, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from a9e36b1 to fd9f479 Compare August 21, 2024 03:53
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.4.1 chore(deps): bump @types/node to 22.4.2 Aug 21, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from fd9f479 to d23f601 Compare August 21, 2024 16:42
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.4.2 chore(deps): bump @types/node to 22.5.0 Aug 21, 2024
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.5.0 chore(deps): bump @types/node to 22.5.1 Aug 28, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from d23f601 to e04e5fa Compare August 28, 2024 01:49
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.5.1 chore(deps): bump @types/node to 22.5.2 Sep 1, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from e04e5fa to 8fd946f Compare September 1, 2024 14:06
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.5.2 chore(deps): bump @types/node to 22.5.3 Sep 4, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 7f1e38b to b0347db Compare September 5, 2024 00:45
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.5.3 chore(deps): bump @types/node to 22.5.4 Sep 5, 2024
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.5.4 chore(deps): bump @types/node to 22.5.5 Sep 14, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from b0347db to ccb7c5e Compare September 14, 2024 03:21
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from ce398a5 to 1b21267 Compare October 19, 2024 04:56
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.7.6 chore(deps): bump @types/node to 22.7.7 Oct 19, 2024
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.7.7 chore(deps): bump @types/node to 22.7.8 Oct 22, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 1b21267 to b748425 Compare October 22, 2024 05:20
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.7.8 chore(deps): bump @types/node to 22.7.9 Oct 23, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from b748425 to 9ea7527 Compare October 23, 2024 04:23
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.7.9 chore(deps): bump @types/node to 22.8.0 Oct 25, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 888e1f2 to 5de86b6 Compare October 25, 2024 22:36
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.8.0 chore(deps): bump @types/node to 22.8.1 Oct 25, 2024
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.8.1 chore(deps): bump @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 c09ea86 to 60d2997 Compare October 29, 2024 16:19
@renovate renovate bot changed the title chore(deps): bump @types/node to 22.8.2 chore(deps): bump node to 22.11.0 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from 8a5da39 to b3597c1 Compare November 5, 2024 03:07
@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from a693a08 to 5ff55f3 Compare November 26, 2024 05:03
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 26eca1f to f506e68 Compare December 3, 2024 22:49
@renovate renovate bot changed the title chore(deps): bump node to 22.11.0 chore(deps): bump node to 22.12.0 Dec 3, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from f506e68 to 6da5bc4 Compare December 11, 2024 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants