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

build(deps): update node.js to v22 #144

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 Oct 29, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines major 20.x -> 22.x age adoption passing confidence
@types/node (source) dependencies major 20.17.16 -> 22.10.9 age adoption passing confidence
@types/node (source) devDependencies major 20.17.16 -> 22.10.9 age adoption passing confidence
node (source) major 20 -> 22 age adoption passing confidence

Release Notes

nodejs/node (node)

v22.13.1

Compare Source

v22.13.0

Compare Source

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.

Copy link

vercel bot commented Oct 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
interval.so ⬜️ Ignored (Inspect) Visit Preview Jan 23, 2025 1:18pm

@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 323187a to 778a608 Compare October 29, 2024 17:54
@renovate renovate bot changed the title build(deps): update dependency @types/node to v22 build(deps): update node.js to v22 Oct 29, 2024
@renovate renovate bot force-pushed the renovate/node-22.x branch from 778a608 to f571121 Compare October 29, 2024 19:44
@renovate renovate bot force-pushed the renovate/node-22.x branch from f571121 to aa1938d Compare October 29, 2024 22:27
@renovate renovate bot force-pushed the renovate/node-22.x branch from aa1938d to ecfc9b1 Compare October 31, 2024 03:47
@renovate renovate bot force-pushed the renovate/node-22.x branch from ecfc9b1 to 6494748 Compare October 31, 2024 06:10
Copy link

vercel bot commented Oct 31, 2024

Deployment failed with the following error:

Resource is limited - try again in 23 minutes (more than 100, code: "api-deployments-free-per-day").

@renovate renovate bot force-pushed the renovate/node-22.x branch from 6494748 to 3886d9a Compare October 31, 2024 09:32
Copy link

vercel bot commented Oct 31, 2024

Deployment failed with the following error:

Resource is limited - try again in 33 minutes (more than 100, code: "api-deployments-free-per-day").

Copy link

vercel bot commented Oct 31, 2024

Deployment failed with the following error:

Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").

@renovate renovate bot force-pushed the renovate/node-22.x branch from faa6a7a to 8655c8e Compare November 3, 2024 05:03
Copy link

vercel bot commented Nov 3, 2024

Deployment failed with the following error:

Resource is limited - try again in 26 seconds (more than 100, code: "api-deployments-free-per-day").

@renovate renovate bot force-pushed the renovate/node-22.x branch from 8655c8e to 1073b8c Compare November 3, 2024 07:14
Copy link

vercel bot commented Nov 3, 2024

Deployment failed with the following error:

Resource is limited - try again in 37 minutes (more than 100, code: "api-deployments-free-per-day").

@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 64b1bd7 to c00e33d Compare November 28, 2024 11:01
Copy link

vercel bot commented Nov 28, 2024

Deployment failed with the following error:

Resource is limited - try again in 14 minutes (more than 100, code: "api-deployments-free-per-day").

@renovate renovate bot force-pushed the renovate/node-22.x branch 5 times, most recently from 56683a8 to 1d0a5de Compare December 11, 2024 15:17
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from fe05dd7 to 8810193 Compare December 16, 2024 19:28
@renovate renovate bot force-pushed the renovate/node-22.x branch 2 times, most recently from 0043d64 to 3f054bd Compare December 26, 2024 19:43
@renovate renovate bot force-pushed the renovate/node-22.x branch 6 times, most recently from 0f4c965 to 9c2183a Compare January 3, 2025 08:18
@renovate renovate bot force-pushed the renovate/node-22.x branch 6 times, most recently from d8f59ab to f84f392 Compare January 16, 2025 04:20
@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from ca5d297 to 82cf374 Compare January 23, 2025 10:27
@renovate renovate bot force-pushed the renovate/node-22.x branch from 82cf374 to 3290b0e Compare January 23, 2025 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants