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.

Sign up for GitHub

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

Jump to bottom

Update Node.js to v22 #52

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

Update Node.js to v22 #52

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 9, 2022 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
node (source) volta major 18.12.0 -> 22.12.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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 this update 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 force-pushed the renovate/major-front-end-dependencies branch from f764148 to 8b85b90 Compare November 16, 2022 23:47
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch from 8b85b90 to 913b966 Compare November 27, 2022 18:57
@renovate renovate bot changed the title Update dependency npm to v9 Update front end dependencies (major) Nov 27, 2022
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from c178395 to 98cfbb2 Compare November 30, 2022 23:56
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from aab2658 to 4a49d02 Compare December 10, 2022 16:41
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from 54ce5b9 to 7a9ce34 Compare December 22, 2022 12:40
@renovate
Copy link
Contributor Author

renovate bot commented Dec 22, 2022 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"9.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"7.8.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-07T15_57_32_561Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch from 7a9ce34 to 1ecb66c Compare December 22, 2022 18:58
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 3 times, most recently from e89d601 to ff77434 Compare January 12, 2023 23:47
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 4 times, most recently from 350c9b1 to ae48053 Compare January 24, 2023 16:34
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch from ae48053 to 67cef8b Compare January 26, 2023 00:47
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from b99b54a to 69b6af7 Compare February 8, 2023 01:17
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from 78f2580 to c592916 Compare February 22, 2023 19:42
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from a928155 to 04de782 Compare March 2, 2023 13:32
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 5 times, most recently from f6d67bf to f5ea3fa Compare March 13, 2023 21:30
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 4 times, most recently from e02b2e1 to 3c96e2c Compare October 12, 2024 08:30
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 3 times, most recently from ef00c18 to 4315015 Compare October 21, 2024 20:05
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 3 times, most recently from 24264c2 to e03d4e6 Compare November 2, 2024 08:38
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 3 times, most recently from f908861 to a86c099 Compare November 11, 2024 17:51
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 5 times, most recently from 9c4ad7d to eb7d3e3 Compare November 21, 2024 17:53
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 5 times, most recently from 6609872 to bcc9b30 Compare November 30, 2024 00:37
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from 764e9b0 to 7eec44c Compare December 5, 2024 08:59
@renovate renovate bot changed the title Update front end dependencies (major) Update Node.js to v22 Dec 8, 2024
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch 2 times, most recently from 055c6e3 to 03fff7c Compare December 14, 2024 02:38
@renovate renovate bot force-pushed the renovate/major-front-end-dependencies branch from 03fff7c to 0e2ba39 Compare December 16, 2024 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants