chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@testing-library/jest-dom	6.4.2 -> 6.4.5					devDependencies	patch
@types/node (source)	20.12.7 -> 20.12.13					devDependencies	patch
@types/react (source)	18.2.76 -> 18.3.3					devDependencies	minor
@types/react-dom (source)	18.2.25 -> 18.3.0					devDependencies	minor
@typescript-eslint/eslint-plugin (source)	7.6.0 -> 7.11.0					devDependencies	minor
@typescript-eslint/parser (source)	7.6.0 -> 7.11.0					devDependencies	minor
clsx	2.1.0 -> 2.1.1					dependencies	patch
eslint-config-next (source)	14.2.0 -> 14.2.3					devDependencies	patch
mongodb	6.5.0 -> 6.7.0					dependencies	minor
next (source)	14.2.0 -> 14.2.3					dependencies	patch
node (source)	20.12.2 -> 20.14.0						minor
node	20.12.2-alpine3.19 -> 20.14.0-alpine3.19					final	minor
nodemon (source)	3.1.0 -> 3.1.2					devDependencies	patch
react (source)	18.2.0 -> 18.3.1					dependencies	minor
react-dom (source)	18.2.0 -> 18.3.1					dependencies	minor
react-resizable-panels	2.0.16 -> 2.0.19					dependencies	patch
tailwind-merge	2.2.2 -> 2.3.0					dependencies	minor
ts-jest (source)	29.1.2 -> 29.1.4					devDependencies	patch
zod (source)	3.22.4 -> 3.23.8					dependencies	minor

---

Release Notes

testing-library/jest-dom (@​testing-library/jest-dom)

v6.4.5

Compare Source

Bug Fixes

• add js suffix to isEqualWith import (#​599) (e8c8b13)

v6.4.4

Compare Source

v6.4.3

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.11.0

Compare Source

🚀 Features

• eslint-plugin: deprecate prefer-ts-expect-error in favor of ban-ts-comment

🩹 Fixes

• eslint-plugin: [consistent-type-assertions] prevent syntax errors on arrow functions

❤️ Thank You

• Abraham Guo
• auvred
• Dom Armstrong
• Kirk Waiblinger

You can read about our versioning strategy and releases on our website.

v7.10.0

Compare Source

🚀 Features

• eslint-plugin: [sort-type-constituents] support case sensitive sorting

🩹 Fixes

• eslint-plugin: [prefer-regexp-exec] fix heuristic to check whether regex may contain global flag

❤️ Thank You

• auvred
• Emanuel Hoogeveen
• jsfm01
• Kirk Waiblinger

You can read about our versioning strategy and releases on our website.

v7.9.0

Compare Source

🩹 Fixes

• eslint-plugin: [explicit-function-return-types] fix false positive on default parameters

❤️ Thank You

• Kirk Waiblinger
• Sheetal Nandi
• Vinccool96

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-unsafe-argument] handle tagged templates

• eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check

• eslint-plugin: [consistent-type-assertions] handle tagged templates

• eslint-plugin: [no-unsafe-return] handle union types

• eslint-plugin: [no-unused-vars] clear error report range

❤️ Thank You

• auvred
• Josh Goldberg ✨
• jsfm01
• Kim Sang Du
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment

• eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type

• eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish

• eslint-plugin: [no-for-in-array] refine report location

• eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type

❤️ Thank You

• Abraham Guo
• Kirk Waiblinger
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

🚀 Features

• eslint-plugin: replace no-new-symbol with no-new-native-nonconstructor

❤️ Thank You

• Dave
• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.11.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.10.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.9.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.8.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

lukeed/clsx (clsx)

v2.1.1

Compare Source

Patches

• (types) Include bigint in ClassValue type: (#​96): 3d960ab
  Accommodates recent @types/react changes to ReactNode.
  Thank you @​ViliamKopecky~!

Chores

• Add licenses.dev badge: 684509c
  This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

---

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

vercel/next.js (eslint-config-next)

v14.2.3

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

mongodb/node-mongodb-native (mongodb)

v6.7.0

Compare Source

Features

• NODE-5464: OIDC machine and callback workflow (#​3912) (2ba8434)

Bug Fixes

• NODE-6165: useBigInt64 causes compareTopologyVersion to throw (#​4109) (21b729b)

v6.6.2

Compare Source

Bug Fixes

• NODE-6171: RTT set to zero when serverMonitoringMode=stream (#​4110) (7a7ec5b)

v6.6.1

Compare Source

Bug Fixes

• NODE-6151: MongoClient connect does not keep Node.js running (#​4101) (7e0d9e6)

v6.6.0

Compare Source

The MongoDB Node.js team is pleased to announce version 6.6.0 of the mongodb package!

Release Notes

Aggregation pipelines can now add stages manually

When creating an aggregation pipeline cursor, a new generic method addStage() has been added in the fluid API for users to add aggregation pipeline stages in a general manner.

const documents = await users.aggregate().addStage({ $project: { name: true } }).toArray();

Thank you @​prenaissance for contributing this feature!

cause and package name included for MongoMissingDependencyErrors

MongoMissingDependencyErrors now include a cause and a dependencyName field, which can be used to programmatically determine which package is missing and why the driver failed to load it.

For example:

MongoMissingDependencyError: The iHateJavascript module does not exist
    at findOne (mongodb/main.js:7:11)
    at Object.<anonymous> (mongodb/main.js:14:1)
    ... 3 lines matching cause stack trace ...
    at Module._load (node:internal/modules/cjs/loader:1021:12) {
  dependencyName: 'iHateJavascript',
  [Symbol(errorLabels)]: Set(0) {},
  [cause]: Error: Cannot find module 'iHateJavascript'
  Require stack:
  - mongodb/main.js
      at require (node:internal/modules/helpers:179:18)
      at findOne (mongodb/main.js:5:5)
      at Object.<anonymous> (mongodb/main.js:14:1) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [ 'mongodb/main.js' ]
  }
}

ServerDescription Round Trip Time (RTT) measurement changes

(1) ServerDescription.roundTripTime is now a moving average

Previously, ServerDescription.roundTripTime was calculated as a weighted average of the most recently observed heartbeat duration and the previous duration. This update changes this behaviour to average ServerDescription.roundTripTime over the last 10 observed heartbeats. This should reduce the likelihood that the selected server changes as a result of momentary spikes in server latency.

(2) Added minRoundTripTime to ServerDescription

A new minRoundTripTime property is now available on the ServerDescription class which gives the minimum RTT over the last 10 heartbeats. Note that this value will be reported as 0 when fewer than 2 samples have been observed.

type supported in SearchIndexDescription

It is now possible to specify the type of a search index when creating a search index:

const indexName = await collection.createSearchIndex({
  name: 'my-vector-search-index',
  // new! specifies that a `vectorSearch` index is created
  type: 'vectorSearch',
  definition: {
    mappings: { dynamic: false }
  }
});

Collection.findOneAndModify's UpdateFilter.$currentDate no longer throws on collections with limited schema

Example:

// collection has no schema
collection.update(
    $currentData: {
       lastModified: true
    } // no longer throws a TS error
);

TopologyDescription now properly stringifies itself to JSON

The TopologyDescription class is exposed by the driver in server selection errors and topology monitoring events to provide insight into the driver's current representation of the server's topology and to aid in debugging. However, the TopologyDescription uses Maps internally, which get serialized to {} when JSON stringified. We recommend using Node's util.inspect() helper to print topology descriptions because inspect properly handles all JS types and all types we use in the driver. However, if JSON must be used, the TopologyDescription now provides a custom toJSON() hook:

client.on('topologyDescriptionChanged', ({ newDescription }) => {
   // recommended!
	console.log('topology description changed', inspect(newDescription, { depth: Infinity, colors: true }))

    // now properly prints the entire topology description
	console.log('topology description changed', JSON.stringify(newDescription))
});

Omit readConcern and writeConcern in Collection.listSearchIndexes options argument

[!Important]
readConcern and writeConcern are no longer viable keys in the options argument passed into Collection.listSearchIndexes

This type change is a correctness fix.

Collection.listSearchIndexes is an Atlas specific method, and Atlas' search indexes do not support readConcern and writeConcern options. The types for this function now reflect this functionality.

Don't throw error when non-read operation in a transaction has a ReadPreferenceMode other than 'primary'

The following error will now only be thrown when a user provides a ReadPreferenceMode other than primary and then tries to perform a command that involves a read:

new MongoTransactionError('Read preference in a transaction must be primary');

Prior to this change, the Node Driver would incorrectly throw this error even when the operation does not perform a read.
Note: a RunCommandOperation is treated as a read operation for this error.

TopologyDescription.error type is MongoError

[!Important]
The TopologyDescription.error property type is now MongoError rather than MongoServerError.

This type change is a correctness fix.

Before this change, the following errors that were not instances of MongoServerError were already passed into TopologyDescription.error at runtime:

• MongoNetworkError (excluding MongoNetworkRuntimeError)
• MongoError with a MongoErrorLabel.HandshakeError label

indexExists() no longer supports the full option

The Collection.indexExists() helper supported an option, full, that modified the internals of the method. When full was set to true, the driver would always return false, regardless of whether or not the index exists.

The full option is intended to modify the return type of index enumeration APIs (Collection.indexes() and Collection.indexInformation(), but since the return type of Collection.indexExists() this option does not make sense for the Collection.indexExists() helper.

We have removed support for this option.

indexExists(), indexes() and indexInformation() support cursor options in Typescript

These APIs have supported cursor options at runtime since the 4.x version of the driver, but our Typescript has incorrectly omitted cursor options from these APIs.

Index information helpers have accurate Typescript return types

Collection.indexInformation(), Collection.indexes() and Db.indexInformation() are helpers that return index information for a given collection or database. These helpers take an option, full, that configures whether the return value contains full index descriptions or a compact summary:

collection.indexes({ full: true });   // returns an array of index descriptions
collection.indexes({ full: false });  // returns an object, mapping index names to index keys

However, the Typescript return type of these helpers was always Document. Thanks to @​prenaissance, these helpers now have accurate type information! The helpers return a new type, IndexDescriptionCompact | IndexDescriptionInfo[], which accurately reflects the return type of these helpers. The helpers also support type narrowing by providing a boolean literal as an option to the API:

collection.indexes();   // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
collection.indexes({ full: false });  // returns an `IndexDescriptionCompact`
collection.indexes({ full: true });  // returns an `IndexDescriptionInfo[]`

collection.indexInfo();   // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
collection.indexInfo({ full: false });  // returns an `IndexDescriptionCompact`
collection.indexInfo({ full: true });  // returns an `IndexDescriptionInfo[]`

db.indexInfo();   // returns `IndexDescriptionCompact | IndexDescriptionInfo[]`
db.indexInfo({ full: false });  // returns an `IndexDescriptionCompact`
db.indexInfo({ full: true });  // returns an `IndexDescriptionInfo[]`

AWS credentials with expirations no longer throw when using on-demand AWS KMS credentials

In addition to letting users provide KMS credentials manually, client-side encryption supports fetching AWS KMS credentials on-demand using the AWS SDK. However, AWS credential mechanisms that returned access keys with expiration timestamps caused the driver to throw an error.

The driver will no longer throw an error when receiving an expiration token from the AWS SDK.

ClusterTime interface signature optionality

The ClusterTime interface incorrectly reported the signature field as required, the server may omit it, so the typescript has been updated to reflect reality.

Summary

Features

• NODE-3639: add a general stage to the aggregation pipeline builder (#​4079) (8fca1aa)
• NODE-5678: add options parsing support for timeoutMS and defaultTimeoutMS (#​4068) (ddd1e81)
• NODE-5762: include cause and package name for all MongoMissingDependencyErrors (#​4067) (62ea94b)
• NODE-5825: add minRoundTripTime to ServerDescription and change roundTripTime to a moving average (#​4059) (0e3d6ea)
• NODE-5919: support new type option in create search index helpers (#​4060) (3598c23)
• NODE-6020: upgrade bson to ^6.5.0 (#​4035) (8ab2055)
• NODE-6149: upgrade bson to ^6.7.0 (#​4099) (7f191cf)

Bug Fixes

• NODE-3681: Typescript error in Collection.findOneAndModify UpdateFilter.$currentDate (#​4047) (a8670a7)
• NODE-5530: make topology descriptions JSON stringifiable (#​4070) (3a0e011)
• NODE-5745: ignore Read/Write Concern in Atlas Search Index Helpers (#​4042) (67d7bab)
• NODE-5925: driver throws error when non-read operation in a transaction has a ReadPreferenceMode other than primary (#​4075) (39fc198)
• NODE-5971: attach v to createIndexes command when version is specified (#​4043) (1879a04)
• NODE-5999: Change TopologyDescription.error type to MongoError (#​4028) (30432e8)
• NODE-6019: indexExists always returns false when full is set to true (#​4034) (0ebc1ac)
• NODE-6029: update types for collection listing indexes (#​4072) (232bf3c)
• NODE-6051: only provide expected allowed keys to libmongocrypt after fetching AWS KMS credentials (#​4057) (c604e74)
• NODE-6066: ClusterTime.signature can be undefined (#​4069) (ce55ca9)

Performance Improvements

• NODE-6127: move error construction into setTimeout callback (#​4094) (6abc074)

Documentation

• Reference
• API
• Changelog

We invite you to try the mongodb library immediately, and report any issues to the NODE project.

vercel/next.js (next)

v14.2.3

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

nodejs/node (node)

v20.14.0

Compare Source

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits

• [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0

Compare Source

remy/nodemon (nodemon)

v3.1.2

Compare Source

v3.1.1

Compare Source

Bug Fixes

• add types to help with required nodemon usage (#​2204) (cd27c0b)

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

bvaughn/react-resizable-panels (react-resizable-panels)

v2.0.19

Compare Source

v2.0.18

Compare Source

v2.0.17

Compare Source

• Prevent pointer events handled by resize handles from triggering elements behind/underneath (#​338)

dcastil/tailwind-merge (tailwind-merge)

v2.3.0

Compare Source

New Features

• Add support for mix-blend-plus-darker utility by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/403
• Added support for bigint in ClassNameValue type by @​LarsArtmann in https://github.com/dcastil/tailwind-merge/pull/402

Documentation

• Add tailwind-merge-go to similar packages in docs by @​Oudwins in https://github.com/dcastil/tailwind-merge/pull/396

Full Changelog: dcastil/tailwind-merge@v2.2.2...v2.3.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy and @​jamesreaco for sponsoring tailwind-merge! ❤️

kulshekhar/ts-jest (ts-jest)

v29.1.4

Compare Source

Bug Fixes

• fix(transformer): allow transforming of .cts/.mts extensions. (#​3996) (b8f6eaa), closes #​3996

Features

• feat: make cli generate esm config based on type: "module" (#​4210) (81a5f64), closes #​4210 #​4012

v29.1.3

Compare Source

Bug Fixes

• add @jest/transform as an optional peer dependency (0ba7f86)
• bring back Node 14 support (eda56a7)

Performance Improvements

• remove ts resolved module cache file (4c88da5)

colinhacks/zod (zod)

v3.23.8

Compare Source

Commits:

• 0f4d403 Add Bronze logos (#​3470)
• 1968731 Tweak tiers (#​3471)
• eda7df3 Change RefinementCtx to interface
• ca42965 v3.23.8

v3.23.7

Compare Source

v3.23.6

Compare Source

v3.23.5

Compare Source

v3.23.4

Compare Source

Commits:

• 157b18d Add 3.23 announcement
• aedf93f Revert change to default Input
• 45107f7 v3.23.4

v3.23.3

Compare Source

v3.23.2

Compare Source

Commits:

• c340558 Update protocol
• ef588d0 Fix t3env
• 9df70dd 3.23.2

v3.23.1

Compare Source

v3.23.0

Compare Source

Zod 3.23 is now available. This is the final 3.x release before Zod 4.0. To try it out:

npm install zod

Features

z.string().date()

Zod can now validate ISO 8601 date strings. Thanks @​igalklebanov! https://github.com/colinhacks/zod/pull/1766

const schema = z.string().date();
schema.parse("2022-01-01"); // OK

z.string().time()

Zod can now validate ISO 8601 time strings. Thanks @​igalklebanov! https://github.com/colinhacks/zod/pull/1766

const schema = z.string().time();
schema.parse("12:00:00"); // OK

You can specify sub-second precision using the precision option:

const schema = z.string().time({ precision: 3 });
schema.parse("12:00:00.123"); // OK
schema.parse("12:00:00.123456"); // Error
schema.parse("12:00:00"); // Error

z.string().duration()

Zod can now validate ISO 8601 duration strings. Thanks @​mastermatt! https://github.com/colinhacks/zod/pull/3265

const schema = z.string().duration();
schema.parse("P3Y6M4DT12H30M5S"); // OK

Improvements to z.string().datetime()

Thanks @​bchrobot https://github.com/colinhacks/zod/pull/2522

You can now allow unqualified (timezone-less) datetimes using the local: true flag.

const schema = z.string().datetime({ local: true });
schema.parse("2022-01-01T12:00:00"); // OK

Plus, Zod now validates the day-of-month correctly to ensure no invalid dates (e.g. February 30th) pass validation. Thanks @​szamanr! https://github.com/colinhacks/zod/pull/3391

z.string().base64()

Zod can now validate base64 strings. Thanks @​StefanTerdell! https://github.com/colinhacks/zod/pull/3047

const schema = z.string().base64();
schema.parse("SGVsbG8gV29ybGQ="); // OK

Improved discriminated unions

The following can now be used as discriminator keys in z.discriminatedUnion():

• ZodOptional
• ZodNullable
• ZodReadonly
• ZodBranded
• ZodCatch

const schema = z.discriminatedUnion("type", [
  z.object({ type: z.literal("A").optional(), value: z.number() }),
  z.object({ type: z.literal("B").nullable(), value: z.string() }),
  z.object({ type: z.literal("C").readonly(), value: z.boolean() }),
  z.object({ type: z.literal("D").brand<"D">(), value: z.boolean() }),
  z.object({ type: z.literal("E").catch("E"), value: z.unknown() }),
]);

Misc

• feature: allow falsy error message by @​fernandollisboa in https://github.com/colinhacks/zod/pull/3178
• feature: add attribute message to enum validatiion by @​fernandollisboa in https://github.com/colinhacks/zod/pull/3169

Breaking changes

There are no breaking changes to the public API of Zod. However some changes can impact ecosystem tools that rely on Zod internals.

ZodFirstPartySchemaTypes

Three new types have been added to the ZodFirstPartySchemaTypes union. This may impact some codegen libraries. https://github.com/colinhacks/zod/pull/3247

+  | ZodPipeline<any, any>
+  | ZodReadonly<any>
+  | ZodSymbol;

Default generics in ZodType

The third argument of the ZodType base class now defaults to unknown. This makes it easier to define recursive schemas and write generic functions that accept Zod schemas.

- class ZodType<Output = any, Def extends ZodTypeDef = ZodTypeDef, Input = Output> {}
+ class ZodType<Output = unknown, Def extends ZodTypeDef = ZodTypeDef, Input = unknown> {}

Unrecognized keys in .pick() and .omit()

This version fixes a bug where unknown keys were accidentally accepted in .pick() and omit(). This has been fixed, which could cause compiler errors in some user code. https://github.com/colinhacks/zod/pull/3255

z.object({ 
  name: z.string() 
}).pick({
  notAKey: true // no longer allowed
})

Bugfixes and performance

• Bugfix: Enum.extract/exclude should not remove error mapping by @​shaharke in https://github.com/colinhacks/zod/pull/3240
• Added latest stable Node and TypeScript versions to test matrix for up-to-date testing. by @​m10rten in https://github.com/colinhacks/zod/pull/3278
• Add types to ZodFirstPartySchemaTypes by @​MatthijsMud in https://github.com/colinhacks/zod/pull/3247
• fix: make input of .required() readonly by @​KATT in https://github.com/colinhacks/zod/pull/3301
• add never props to safe parse return types by @​schicks in https://github.com/colinhacks/zod/pull/3295
• Reporting errors of the preprocess that is the second property of object by @​yukukotani in https://github.com/colinhacks/zod/pull/2912
• Improve addQuestionMarks, fix #​2184 by [@​colinh

---

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.

👻 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 Mend Renovate. View repository job log here.