fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@apollo/client (source)	3.7.15 -> 3.10.4					dependencies	minor
@babel/core (source)	7.22.5 -> 7.24.7					devDependencies	minor
@babel/eslint-parser (source)	7.22.5 -> 7.24.7					devDependencies	minor
@headlessui/react (source)	1.7.15 -> 1.7.19					dependencies	patch
@heroicons/react	2.0.18 -> 2.1.3					dependencies	minor
@hookform/resolvers (source)	3.1.1 -> 3.6.0					dependencies	minor
@rainbow-me/rainbowkit (source)	0.12.14 -> 0.12.18					dependencies	patch
@rainbow-me/rainbowkit-siwe-next-auth (source)	0.2.0 -> 0.4.1					dependencies	minor
@storybook/addon-essentials (source)	7.0.20 -> 7.6.19					devDependencies	minor
@storybook/addon-interactions (source)	7.0.20 -> 7.6.19					devDependencies	minor
@storybook/addon-links (source)	7.0.20 -> 7.6.19					devDependencies	minor
@storybook/nextjs (source)	7.0.20 -> 7.6.19					devDependencies	minor
@storybook/react (source)	7.0.20 -> 7.6.19					devDependencies	minor
@storybook/testing-library	0.1.0 -> 0.2.2					devDependencies	minor
@tailwindcss/forms	0.5.3 -> 0.5.7					dependencies	patch
@testing-library/jest-dom	5.16.5 -> 5.17.0					devDependencies	minor
@testing-library/react	14.0.0 -> 14.3.1					devDependencies	minor
@trivago/prettier-plugin-sort-imports	4.1.1 -> 4.3.0					devDependencies	minor
@types/react (source)	18.2.12 -> 18.3.3					devDependencies	minor
@typescript-eslint/eslint-plugin (source)	5.59.11 -> 5.62.0					devDependencies	minor
@typescript-eslint/parser (source)	5.59.11 -> 5.62.0					devDependencies	minor
@vitest/ui (source)	0.32.0 -> 0.34.7					devDependencies	minor
autoprefixer	10.4.14 -> 10.4.19					devDependencies	patch
babel-jest (source)	29.5.0 -> 29.7.0					devDependencies	minor
babel-loader	9.1.2 -> 9.1.3					devDependencies	patch
class-variance-authority	0.6.0 -> 0.7.0					dependencies	minor
concurrently	8.2.0 -> 8.2.2					devDependencies	patch
eslint (source)	8.42.0 -> 8.57.0					devDependencies	minor
eslint-config-next (source)	13.4.5 -> 13.5.6					devDependencies	minor
eslint-config-prettier	8.8.0 -> 8.10.0					devDependencies	minor
eslint-plugin-storybook	0.6.12 -> 0.8.0					devDependencies	minor
graphql	16.6.0 -> 16.8.1					dependencies	minor
lint-staged	13.2.2 -> 13.3.0					devDependencies	minor
loglevel	1.8.1 -> 1.9.1					dependencies	minor
msw (source)	1.2.2 -> 1.3.3					devDependencies	minor
next (source)	13.4.5 -> 13.5.6					dependencies	minor
next-auth (source)	4.22.1 -> 4.24.7					dependencies	minor
next-validations	0.3.2 -> 0.4.2					dependencies	minor
node (source)	18.16.0 -> 18.20.3						minor
postcss (source)	8.4.24 -> 8.4.38					resolutions	patch
postcss (source)	8.4.24 -> 8.4.38					devDependencies	patch
react (source)	18.2.0 -> 18.3.1					dependencies	minor
react-dom (source)	18.2.0 -> 18.3.1					dependencies	minor
react-hook-form (source)	7.44.3 -> 7.51.5					dependencies	minor
rustywind	0.16.0 -> 0.22.0					devDependencies	minor
siwe	2.1.4 -> 2.3.2					dependencies	minor
sort-package-json	2.4.1 -> 2.10.0					devDependencies	minor
storybook (source)	7.0.20 -> 7.6.19					devDependencies	minor
tailwindcss (source)	3.3.2 -> 3.4.4					devDependencies	minor
typescript (source)	5.1.3 -> 5.4.5					devDependencies	minor
vite (source)	4.3.9 -> 4.5.3					devDependencies	minor
vitest (source)	0.32.0 -> 0.34.6					devDependencies	minor
wagmi (source)	0.12.15 -> 0.12.19					dependencies	patch
yup	1.2.0 -> 1.4.0					dependencies	minor

---

Release Notes

apollographql/apollo-client (@​apollo/client)

v3.10.4

Compare Source

Patch Changes

• #​11838 8475346 Thanks @​alex-kinokon! - Don’t prompt for DevTools installation for browser extension page

• #​11839 6481fe1 Thanks @​jerelmiller! - Fix a regression in 3.9.5 where a merge function that returned an incomplete result would not allow the client to refetch in order to fulfill the query.

• #​11844 86984f2 Thanks @​jerelmiller! - Honor the @nonreactive directive when using cache.watchFragment or the useFragment hook to avoid rerendering when using these directives.

• #​11824 47ad806 Thanks @​phryneas! - Create branded QueryRef type without exposed properties.

  This change deprecates QueryReference in favor of a QueryRef type that doesn't expose any properties.
  This change also updates preloadQuery to return a new PreloadedQueryRef type, which exposes the toPromise function as it does today. This means that query refs produced by useBackgroundQuery and useLoadableQuery now return QueryRef types that do not have access to a toPromise function, which was never meant to be used in combination with these hooks.

  While we tend to avoid any types of breaking changes in patch releases as this, this change was necessary to support an upcoming version of the React Server Component integration, which needed to omit the toPromise function that would otherwise have broken at runtime.
  Note that this is a TypeScript-only change. At runtime, toPromise is still present on all queryRefs currently created by this package - but we strongly want to discourage you from accessing it in all cases except for the PreloadedQueryRef use case.

  Migration is as simple as replacing all references to QueryReference with QueryRef, so it should be possible to do this with a search & replace in most code bases:

  -import { QueryReference } from '@​apollo/client'
  +import { QueryRef } from '@​apollo/client'
  
  - function Component({ queryRef }: { queryRef: QueryReference<TData> }) {
  + function Component({ queryRef }: { queryRef: QueryRef<TData> }) {
    // ...
  }

• #​11845 4c5c820 Thanks @​jerelmiller! - Remove @nonreactive directives from queries passed to MockLink to ensure they are properly matched.

• #​11837 dff15b1 Thanks @​jerelmiller! - Fix an issue where a polled query created in React strict mode may not stop polling after the component unmounts while using the cache-and-network fetch policy.

v3.10.3

Compare Source

Patch Changes

• #​11811 d67d7f9 Thanks @​phryneas! - Adjust some types for React 19 compat

• #​11834 7d8aad4 Thanks @​psamim! - Fix error "Cannot convert object to primitive value"

v3.10.2

Compare Source

Patch Changes

• #​11821 2675d3c Thanks @​jerelmiller! - Fix a regression where rerendering a component with useBackgroundQuery would recreate the queryRef instance when used with React's strict mode.

• #​11821 2675d3c Thanks @​jerelmiller! - Revert the change introduced in
  3.9.10 via #​11738 that disposed of queryRefs synchronously. This change caused too many issues with strict mode.

v3.10.1

Compare Source

Patch Changes

• #​11792 5876c35 Thanks @​phryneas! - AutoCleanedCache: only schedule batched cache cleanup if the cache is full (fixes #​11790)

• #​11799 1aca7ed Thanks @​phryneas! - RenderPromises: use canonicalStringify to serialize variables to ensure query deduplication is properly applied even when variables are specified in a different order.

• #​11803 bf9dd17 Thanks @​phryneas! - Update the rehackt dependency to ^0.1.0

• #​11756 60592e9 Thanks @​henryqdineen! - Fix operation.setContext() type

v3.10.0

Compare Source

Minor Changes

• #​11605 e2dd4c9 Thanks @​alessbell! - Adds createMockFetch utility for integration testing that includes the link chain

• #​11760 acd1982 Thanks @​alessbell! - createTestSchema now uses graphql-tools mergeResolvers to merge resolvers instead of a shallow merge.

• #​11764 f046aa9 Thanks @​alessbell! - Rename createProxiedSchema to createTestSchema and createMockFetch to createSchemaFetch.

• #​11777 5dfc79f Thanks @​alessbell! - Call createMockSchema inside createTestSchema.

• #​11774 2583488 Thanks @​alessbell! - Add ability to set min and max delay in createSchemaFetch

• #​11605 e2dd4c9 Thanks @​alessbell! - Adds proxiedSchema and createMockSchema testing utilities

• #​11465 7623da7 Thanks @​alessbell! - Add watchFragment method to the cache and expose it on ApolloClient, refactor useFragment using watchFragment.

• #​11743 78891f9 Thanks @​jerelmiller! - Remove alpha designation for queryRef.toPromise() to stabilize the API.

• #​11743 78891f9 Thanks @​jerelmiller! - Remove alpha designation for createQueryPreloader to stabilize the API.

• #​11783 440563a Thanks @​alessbell! - Moves new testing utilities to their own entrypoint, testing/experimental

Patch Changes

• #​11757 9825295 Thanks @​phryneas! - Adjust useReadQuery wrapper logic to work with transported objects.

• #​11771 e72cbba Thanks @​phryneas! - Wrap useQueryRefHandlers in wrapHook.

• #​11754 80d2ba5 Thanks @​alessbell! - Export WatchFragmentOptions and WatchFragmentResult from main entrypoint and fix bug where this wasn't bound to the watchFragment method on ApolloClient.

v3.9.11

Compare Source

Patch Changes

• #​11769 04132af Thanks @​jerelmiller! - Fix an issue where using skipToken or the skip option with useSuspenseQuery in React's strict mode would perform a network request.

v3.9.10

Compare Source

Patch Changes

• #​11738 b1a5eb8 Thanks @​jerelmiller! - Fix an issue where rerendering useBackgroundQuery after the queryRef had been disposed, either via the auto dispose timeout or by unmounting useReadQuery, would cause the queryRef to be recreated potentially resulting in another network request.

• #​11738 b1a5eb8 Thanks @​jerelmiller! - Allow queryRefs to be disposed of synchronously when a suspense hook unmounts. This prevents some situations where using a suspense hook with the same query/variables as the disposed queryRef accidentally used the disposed queryRef rather than creating a new instance.

• #​11670 [`cc5c

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4f8cae8

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.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
lens-demo-app	❌ Failed (Inspect)			Jun 6, 2024 5:02am

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/esbuild@0.18.20	Install script: postinstall Source: node install.js	Source
Telemetry	npm/next@13.5.6	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	package.json
Install scripts	npm/msw@1.3.3	Install script: postinstall Source: node -e "try{require('./config/scripts/postinstall')}catch(e){}"	package.json
Install scripts	npm/rustywind@0.22.0	Install script: install Source: node ./lib/postinstall.js || npm run prepack	package.json
Install scripts	npm/core-js-pure@3.27.2	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"	Source
Install scripts	npm/bigint-buffer@1.1.5	Install script: install Source: npm run rebuild || echo "Couldn't build bindings. Non-native version used."	Source
Install scripts	npm/msw@1.2.2	Install script: postinstall Source: node -e "try{require('./config/scripts/postinstall')}catch(e){}"	Source
Install scripts	npm/esbuild@0.17.16	Install script: postinstall Source: node install.js	Source
Telemetry	npm/next@13.4.5	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	Source
Install scripts	npm/rustywind@0.16.0	Install script: install Source: node ./lib/postinstall.js	Source

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/esbuild@0.18.20
• @SocketSecurity ignore npm/next@13.5.6
• @SocketSecurity ignore npm/msw@1.3.3
• @SocketSecurity ignore npm/rustywind@0.22.0
• @SocketSecurity ignore npm/core-js-pure@3.27.2
• @SocketSecurity ignore npm/bigint-buffer@1.1.5
• @SocketSecurity ignore npm/msw@1.2.2
• @SocketSecurity ignore npm/esbuild@0.17.16
• @SocketSecurity ignore npm/next@13.4.5
• @SocketSecurity ignore npm/rustywind@0.16.0

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.