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

fix(deps): update all node.js updates (major) #3319

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/node (source) ^16.18.48 -> ^22.0.0 age adoption passing confidence devDependencies major
@types/node (source) ^18.17.14 -> ^22.0.0 age adoption passing confidence dependencies major
@vercel/node (source) ^2.15.10 -> ^5.0.0 age adoption passing confidence devDependencies major
node (source) 18 -> 22 age adoption passing confidence major
node (source) 18.x -> 22.x age adoption passing confidence engines major

Release Notes

vercel/vercel (@​vercel/node)

v5.0.0

Compare Source

Major Changes
  • [remix-builder][node][routing-utils] revert path-to-regexp updates (#​12746)

v4.0.0

Compare Source

Major Changes
Patch Changes

v3.2.29

Compare Source

Patch Changes

v3.2.28

Compare Source

Patch Changes

v3.2.27

Compare Source

Patch Changes

v3.2.26

Compare Source

Patch Changes

v3.2.25

Compare Source

Patch Changes

v3.2.24

Compare Source

Patch Changes

v3.2.23

Compare Source

Patch Changes

v3.2.22

Compare Source

Patch Changes

v3.2.21

Compare Source

Patch Changes

v3.2.20

Compare Source

Patch Changes

v3.2.19

Compare Source

Patch Changes

v3.2.18

Compare Source

Patch Changes

v3.2.17

Compare Source

Patch Changes

v3.2.16

Compare Source

Patch Changes

v3.2.15

Compare Source

Patch Changes

v3.2.14

Compare Source

Patch Changes

v3.2.13

Compare Source

Patch Changes

v3.2.12

Compare Source

Patch Changes

v3.2.11

Compare Source

Patch Changes

v3.2.10

Compare Source

Patch Changes

v3.2.9

Compare Source

Patch Changes

v3.2.8

Compare Source

Patch Changes

v3.2.7

Compare Source

Patch Changes

v3.2.6

Compare Source

Patch Changes

v3.2.5

Compare Source

Patch Changes

v3.2.4

Compare Source

Patch Changes

v3.2.3

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes
  • Ignore shouldAddHelpers when exporting a server to match production (#​11738)
Patch Changes
  • Update undici dep to address vulnerabilities (#​11749)

v3.1.7

Compare Source

Patch Changes

v3.1.6

Compare Source

Patch Changes

v3.1.5

Compare Source

Patch Changes

v3.1.4

Compare Source

Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
  • Make waitUntil consistent for Node.js & Edge (#​11553)

v3.0.28

Compare Source

Patch Changes

v3.0.27

Compare Source

Patch Changes

v3.0.26

Compare Source

Patch Changes

v3.0.25

Compare Source

Patch Changes

v3.0.24

Compare Source

Patch Changes

v3.0.23

Compare Source

Patch Changes

v3.0.22

Compare Source

Patch Changes

v3.0.21

Compare Source

Patch Changes

v3.0.20

Compare Source

Patch Changes

v3.0.19

Compare Source

Patch Changes

v3.0.18

Compare Source

Patch Changes

v3.0.17

Compare Source

Patch Changes

v3.0.16

Compare Source

Patch Changes

v3.0.15

Compare Source

Patch Changes

v3.0.14

Compare Source

Patch Changes

v3.0.13

Compare Source

Patch Changes

v3.0.12

Compare Source

Patch Changes

v3.0.11

Compare Source

Patch Changes

v3.0.10

Compare Source

Patch Changes

v3.0.9

Compare Source

Patch Changes
  • Replace usage of fetch with undici.request (#​10767)

v3.0.8

Compare Source

Patch Changes

v3.0.7

Compare Source

Patch Changes

v3.0.6

Compare Source

Patch Changes

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes
  • BREAKING CHANGE: Drop Node.js 14, bump minimum to Node.js 16 (#​10369)
Patch Changes
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 - "* 0-3 * * 1" (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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 🤖 Type: Dependencies Dependency updates or something similar label Dec 4, 2023
Copy link

changeset-bot bot commented Dec 4, 2023

⚠️ No Changeset found

Latest commit: e044c3c

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

Copy link
Contributor

github-actions bot commented Dec 4, 2023

Deploy preview for merchant-center-application-kit ready!

✅ Preview
https://merchant-center-application-dakr2jcq4-commercetools.vercel.app
https://appkit-sha-bb78867a4f672abbe419d55223593e59a488e766.commercetools.vercel.app
https://appkit-pr-3319.commercetools.vercel.app

Built with commit e665124.
This pull request is being automatically deployed with vercel-action

Copy link
Contributor

github-actions bot commented Dec 4, 2023

Deploy preview for application-kit-custom-views ready!

✅ Preview
https://application-kit-custom-views-1bop9dqqt-commercetools.vercel.app
https://appkit-cv-sha-5407855ee765d163bf7b43c1a466a5226ae87b39.commercetools.vercel.app
https://appkit-cv-pr-3319.commercetools.vercel.app

Built with commit b39abb1.
This pull request is being automatically deployed with vercel-action

@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 3f7639c to 5ca8953 Compare December 5, 2023 17:16
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 5ca8953 to ea37b5f Compare December 7, 2023 13:01
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from ea37b5f to 39c5b31 Compare December 13, 2023 09:43
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 39c5b31 to ab01176 Compare December 13, 2023 10:44
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from ab01176 to effe7bc Compare December 14, 2023 12:37
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from effe7bc to 1ecf9c2 Compare December 18, 2023 10:28
@CarlosCortizasCT
Copy link
Contributor

We recently agreed on keeping v18 for node, which is supported until May 2025.

@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 2456017 to 19e876a Compare October 10, 2024 12:56
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 19e876a to 98df232 Compare October 14, 2024 14:32
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 98df232 to 6dc55fe Compare October 29, 2024 01:16
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 6dc55fe to 88a1971 Compare October 29, 2024 15:29
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 88a1971 to 9682642 Compare November 14, 2024 11:16
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 9682642 to 1ddb6e9 Compare November 20, 2024 09:02
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 1ddb6e9 to 79d2803 Compare December 5, 2024 15:34
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 79d2803 to f71ddfc Compare December 10, 2024 11:02
@renovate renovate bot changed the title chore(deps): update all node.js updates (major) fix(deps): update all node.js updates (major) Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant