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

chore(deps): update dependencies (major and minor) to v22 (major) #158

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

chore(deps): update dependencies (major and minor) to v22 (major) #158

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 10, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/node (source) ^20.17.10 -> ^22.0.0 age adoption passing confidence devDependencies major
node (source) 20.18.1 -> 22.13.0 age adoption passing confidence major

Release Notes

nodejs/node (node)

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 - "* * * * 0,6" in timezone Asia/Tokyo, Automerge - "* * * * 0,6" in timezone Asia/Tokyo.

🚦 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 requested a review from hiroki0525 as a code owner May 10, 2024 16:41
@bundlemon BundleMon
Copy link

bundlemon bot commented May 10, 2024 •
edited
Loading

BundleMon

Unchanged files (2)
Status Path Size Limits
✅ index.cjs
 1.69KB -
✅ index.js
 1.68KB -

No change in files bundle size

Final result: ✅

View report in BundleMon website ➡️

Current branch size history | Target branch size history

@renovate renovate bot changed the title chore(deps): update dependency eslint to v9 chore(deps): update dependencies (major and minor) (major) May 24, 2024
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch from 304f406 to c4928aa Compare May 24, 2024 14:22
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 5527597 to c415a7e Compare June 1, 2024 01:12
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch from c415a7e to 3676e0e Compare June 21, 2024 19:06
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch from 3676e0e to 58928ec Compare July 22, 2024 17:38
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 98ae6bb to 211d302 Compare August 5, 2024 19:30
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 3 times, most recently from 7fae930 to 08f0b0c Compare August 12, 2024 19:15
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from f7962e7 to 41811b1 Compare August 19, 2024 19:16
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from ee35762 to cc71f71 Compare September 2, 2024 19:19
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 4 times, most recently from 29061fc to 8397157 Compare September 16, 2024 18:10
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 3 times, most recently from b62ff22 to 0878079 Compare September 27, 2024 19:15
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 5ce73fd to cbf5f70 Compare October 7, 2024 18:23
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 3 times, most recently from cb3f2c0 to b952952 Compare October 18, 2024 23:06
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 5 times, most recently from 5a78e6d to 83411ba Compare October 28, 2024 17:25
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 3 times, most recently from d8c5905 to 2c529ce Compare November 4, 2024 18:53
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from e9faefc to ef7e594 Compare November 18, 2024 18:42
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 6726bf5 to 2ad1b09 Compare December 2, 2024 20:43
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 17c2672 to 1ab9924 Compare December 9, 2024 18:13
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 6e78760 to 57c6ca6 Compare December 23, 2024 19:40
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 8b5184b to 13d747b Compare December 31, 2024 08:39
@renovate renovate bot changed the title chore(deps): update dependencies (major and minor) (major) chore(deps): update dependencies (major and minor) to v22 (major) Dec 31, 2024
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch 2 times, most recently from 53d8971 to de49ab2 Compare January 7, 2025 20:25
@renovate renovate bot force-pushed the renovate/major-dependencies-(major-and-minor) branch from de49ab2 to 817707b Compare January 10, 2025 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hiroki0525 hiroki0525 Awaiting requested review from hiroki0525 hiroki0525 is a code owner

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

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