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 all dependencies (major) #842

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

chore(deps): update all dependencies (major) #842

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 5, 2024 •
edited by renovate-coveo bot
Loading

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 20 -> 22 age adoption passing confidence
query-string-cjs dependencies major ^7.0.0 -> ^9.0.0 age adoption passing confidence

Release Notes

nodejs/node (node)

v22.12.0: 2024-12-03, Version 22.12.0 'Jod' (LTS), @​ruyadorno

Compare Source

Notable Changes
require(esm) is now enabled by default

Support for loading native ES modules using require() had been available on v20.x and v22.x under the command line flag --experimental-require-module, and available by default on v23.x. In this release, it is now no longer behind a flag on v22.x.

This feature is still experimental, and we are looking for user feedback to make more final tweaks before fully stabilizing it. For this reason, on v22.x, when the Node.js instance encounters a native ES module in require() for the first time, it will emit an experimental warning unless require() comes from a path that contains node_modules. If there happens to be any regressions caused by this feature, users can report it to the Node.js issue tracker. Meanwhile this feature can also be disabled using --no-experimental-require-module as a workaround.

With this feature enabled, Node.js will no longer throw ERR_REQUIRE_ESM if require() is used to load a ES module. It can, however, throw ERR_REQUIRE_ASYNC_MODULE if the ES module being loaded or its dependencies contain top-level await. When the ES module is loaded successfully by require(), the returned object will either be a ES module namespace object similar to what's returned by import(), or what gets exported as "module.exports" in the ES module.

Users can check process.features.require_module to see whether require(esm) is enabled in the current Node.js instance. For packages, the "module-sync" exports condition can be used as a way to detect require(esm) support in the current Node.js instance and allow both require() and import to load the same native ES module. See the documentation for more details about this feature.

Contributed by Joyee Cheung in #​55085

Added resizable ArrayBuffer support in Buffer

When a Buffer is created using a resizable ArrayBuffer, the Buffer length will now correctly change as the underlying ArrayBuffer size is changed.

const ab = new ArrayBuffer(10, { maxByteLength: 20 });
const buffer = Buffer.from(ab);
console.log(buffer.byteLength); 10
ab.resize(15);
console.log(buffer.byteLength); 15
ab.resize(5);
console.log(buffer.byteLength); 5

Contributed by James Snell in #​55377

Update root certificates to NSS 3.104

This is the version of NSS that shipped in Firefox 131.0 on 2024-10-01.

Certificates added:

  • FIRMAPROFESIONAL CA ROOT-A WEB
  • TWCA CYBER Root CA
  • SecureSign Root CA12
  • SecureSign Root CA14
  • SecureSign Root CA15

Contributed by Richard Lau in #​55681

Other Notable Changes
  • [4920869935] - (SEMVER-MINOR) assert: make assertion_error use Myers diff algorithm (Giovanni Bucci) #​54862
  • [ccffd3b819] - doc: enforce strict policy to semver-major releases (Rafael Gonzaga) #​55732
  • [acc6806900] - doc: add jazelly to collaborators (Jason Zhang) #​55531
  • [88d91e8bc2] - esm: mark import attributes and JSON module as stable (Nicolò Ribaudo) #​55333
  • [98bfc7dce5] - (SEMVER-MINOR) http: add diagnostic channel http.client.request.created (Marco Ippolito) #​55586
  • [337f61fb25] - (SEMVER-MINOR) lib: add UV_UDP_REUSEPORT for udp (theanarkh) #​55403
  • [1628c48ad6] - (SEMVER-MINOR) net: add UV_TCP_REUSEPORT for tcp (theanarkh) #​55408
  • [457e73f4c9] - (SEMVER-MINOR) sqlite: add support for SQLite Session Extension (Bart Louwers) #​54181
Commits

v22.11.0: 2024-10-29, Version 22.11.0 'Jod' (LTS), @​richardlau

Compare Source

Notable Changes

This release marks the transition of Node.js 22.x into Long Term Support (LTS)
with the codename 'Jod'. The 22.x release line now moves into "Active LTS"
and will remain so until October 2025. After that time, it will move into
"Maintenance" until end of life in April 2027.

Other than updating metadata, such as the process.release object, to reflect
that the release is LTS, no further changes from Node.js 22.10.0 are included.

OpenSSL 3.x

Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the quictls OpenSSL fork).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.

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

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone America/Toronto, Automerge - "after 9:00am and before 12:00pm on tuesday, wednesday, thursday" in timezone America/Toronto.

🚦 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 has been generated by Renovate Bot.

@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from ce2ffb8 to 2c131c8 Compare August 6, 2024 09:18
@renovate renovate bot changed the title chore(deps): update all dependencies to v8 (major) chore(deps): update all dependencies (major) Aug 6, 2024
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 0991688 to 2db84d5 Compare August 12, 2024 18:55
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from d947587 to b378884 Compare August 19, 2024 18:11
@renovate renovate bot force-pushed the renovate/major-all branch 4 times, most recently from 374da3f to 251b4fd Compare August 27, 2024 12:31
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from b1e15ad to b51c15a Compare September 5, 2024 18:29
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from f9e6777 to cd8fbcc Compare September 13, 2024 19:24
@renovate renovate bot requested review from a team as code owners September 13, 2024 19:24
@renovate renovate bot force-pushed the renovate/major-all branch 5 times, most recently from 29b3315 to 3d47557 Compare September 23, 2024 18:15
@renovate renovate bot force-pushed the renovate/major-all branch 11 times, most recently from eac819f to 7b82b52 Compare September 30, 2024 20:11
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 762151f to 6d88a51 Compare October 1, 2024 20:24
@renovate-coveo renovate-coveo bot force-pushed the renovate/major-all branch 3 times, most recently from 46a9dff to d4abdff Compare October 10, 2024 19:42
@renovate-coveo renovate-coveo bot changed the title chore(deps): update all dependencies (major) fix(deps): update dependency query-string-cjs to v9 Oct 10, 2024
@renovate-coveo renovate-coveo bot force-pushed the renovate/major-all branch 2 times, most recently from 15288ad to 01ac94c Compare October 15, 2024 14:26
@renovate-coveo renovate-coveo bot force-pushed the renovate/major-all branch 2 times, most recently from 59aee5c to 7a3d916 Compare October 28, 2024 18:32
@renovate-coveo renovate-coveo bot changed the title fix(deps): update dependency query-string-cjs to v9 chore(deps): update all dependencies (major) Nov 5, 2024
gdostie
gdostie requested changes Nov 14, 2024
View reviewed changes
package.json
@@ -88,7 +88,7 @@
"dependencies": {
"core-js": "^3.37.1",
"exponential-backoff": "^3.1.0",
"query-string-cjs": "npm:query-string@^7.0.0",
"query-string-cjs": "npm:query-string@^9.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one cannot be updated

Suggested change
"query-string-cjs": "npm:query-string@^9.0.0",
"query-string-cjs": "npm:query-string@^7.0.0",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gdostie gdostie gdostie requested changes

@aboissinot-coveo aboissinot-coveo Awaiting requested review from aboissinot-coveo aboissinot-coveo is a code owner automatically assigned from coveo/frontend-foundation

@fpbrault fpbrault Awaiting requested review from fpbrault fpbrault is a code owner automatically assigned from coveo/dx

@y-lakhdar y-lakhdar Awaiting requested review from y-lakhdar y-lakhdar is a code owner automatically assigned from coveo/dx

@fbeaudoincoveo fbeaudoincoveo Awaiting requested review from fbeaudoincoveo fbeaudoincoveo is a code owner automatically assigned from coveo/dx

Requested changes must be addressed to merge this pull request.

Assignees
No one assigned
Labels
bot dependency update renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@gdostie