chore(deps): update all non-major dependencies #63
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the WalkthroughThe recent changes involve updating multiple dependencies and development dependencies in the Changes
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for ef-calc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Additional comments not posted (14)
package.json (14)
19-19: LGTM forzustandupdate.The update from
^4.5.0to^4.5.4is a patch version bump, indicating bug fixes and minor improvements. No action needed.
29-29: LGTM foreslintupdate.The update from
^8.56.0to^8.57.0is a patch version bump, indicating bug fixes and minor improvements. No action needed.
16-16: Verify compatibility forreact.The update from
^18.2.0to^18.3.1is a minor version bump. Check for any changes in rendering behavior or new APIs that might affect your application.Verification successful
No issues found with React update.
The codebase uses
React.StrictModeandcreateRoot, both of which are stable and should not be affected by the update to React^18.3.1. The update is safe to proceed with.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes or new features in `react` that might affect the project. # Test: Fetch release notes for `react` from version 18.2.0 to 18.3.1. gh release view --repo facebook/react --json name,body --jq '.body' | grep -E '18\.2\.0|18\.3\.1'Length of output: 97
Script:
#!/bin/bash # Search for React imports and usage in the codebase to identify potentially affected areas. # Find files importing React rg --glob '!node_modules' "import React" -A 3 # Find usage of React features that might be affected by a version update rg --glob '!node_modules' "React\." -A 3Length of output: 353
26-26: Verify compatibility for@types/react.The update from
^18.2.51to^18.3.3is a minor version bump. Ensure that any changes in React type definitions are compatible with your project's type checking.Verification successful
Minor update for
@types/reactappears safe, but verify if needed.The search revealed minimal and standard usage of React types, such as
React.StrictMode, which are unlikely to be affected by the update from^18.2.51to^18.3.3. However, if you have specific concerns about type usage, consider manually verifying compatibility.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for changes in `@types/react` that might affect type checking. # Test: Fetch release notes for `@types/react` from version 18.2.51 to 18.3.3. gh release view --repo DefinitelyTyped/DefinitelyTyped --json name,body --jq '.body' | grep -E '18\.2\.51|18\.3\.3'Length of output: 115
Script:
#!/bin/bash # Search for TypeScript files using React types to check for potential issues with the updated `@types/react`. # Find all TypeScript files and search for React type imports and usage. rg --files-with-matches --iglob '*.ts' --iglob '*.tsx' 'import.*react' -l | xargs rg 'React\.' -A 3Length of output: 208
17-17: Verify compatibility forreact-dom.The update from
^18.2.0to^18.3.1is a minor version bump. Check for any changes in DOM rendering or new APIs that might affect your application.
23-23: Verify compatibility for@mheob/prettier-config.The update from
^3.2.0to^3.3.1is a minor version bump. Ensure that any new formatting rules or changes are compatible with your project's code style.
30-30: Verify compatibility forprettier.The update from
^3.2.4to^3.3.3is a minor version bump. Ensure that any new formatting rules or changes are compatible with your project's code style.
15-15: Verify compatibility for@vercel/analytics.The update from
^1.1.2to^1.3.1is a minor version bump. Ensure that any new features or changes are compatible with your current implementation.Verification successful
Update to
@vercel/analyticsis compatible.The changes from version
1.1.2to1.3.1include enhancements and bug fixes without any breaking changes. This update should be safe for your project.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes or new features in `@vercel/analytics` that might affect the project. # Test: Fetch release notes for `@vercel/analytics` from version 1.1.2 to 1.3.1. gh release view --repo vercel/analytics --json name,body --jq '.body' | grep -E '1\.1\.2|1\.3\.1'Length of output: 175
Script:
#!/bin/bash # Description: Fetch release notes for all versions of `@vercel/analytics` from version 1.1.2 to 1.3.1. # Test: Fetch release notes for all versions between 1.1.2 and 1.3.1. gh release list --repo vercel/analytics --limit 100 | grep -E '1\.1\.[2-9]|1\.2\.[0-9]+|1\.3\.[0-1]'Length of output: 616
Script:
#!/bin/bash # Description: Fetch detailed release notes for each version of `@vercel/analytics` from 1.1.2 to 1.3.1. # Fetch release notes for each version. for version in 1.1.3 1.1.4 1.2.0 1.2.1 1.2.2 1.3.0 1.3.1; do echo "Release notes for version $version:" gh release view $version --repo vercel/analytics --json body --jq '.body' echo "----------------------------------------" doneLength of output: 3797
32-32: Verify compatibility forvite.The update from
^5.0.12to^5.4.0is a minor version bump. Ensure that any changes in Vite's features or configurations are compatible with your project's build or development process.
27-27: Verify compatibility for@types/react-dom.The update from
^18.2.18to^18.3.0is a minor version bump. Ensure that any changes in React DOM type definitions are compatible with your project's type checking.
24-24: Verify compatibility for@mheob/tsconfig.The update from
^2.0.0to^2.1.0is a minor version bump. Ensure that any changes in TypeScript configuration are compatible with your project's build process.
31-31: Verify compatibility fortypescript.The update from
^5.3.3to^5.5.4is a minor version bump. Ensure that any changes in TypeScript features or type definitions are compatible with your project's type checking or build process.
28-28: Verify compatibility for@vitejs/plugin-react.The update from
^4.2.1to^4.3.1is a minor version bump. Ensure that any changes in Vite's React plugin are compatible with your project's build or development process.Verification successful
Compatibility Confirmed for
@vitejs/plugin-reactUpdateThe update to version
4.3.1includes a fix that enhances support for the React Compiler with React 18. This change allows the compiler to be used with React 18 and a customruntimeModule, correcting a previous assumption that it was only usable with React 19. Ensure that your project aligns with these changes, especially if you are using a customruntimeModule. No breaking changes were found that would impact typical usage.
- Release Note: Fix support for React Compiler with React 18.
- Action: Verify if your project uses a custom
runtimeModuleand update accordingly.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for changes in `@vitejs/plugin-react` that might affect the build or development process. # Test: Fetch release notes for `@vitejs/plugin-react` from version 4.2.1 to 4.3.1. gh release view --repo vitejs/vite --json name,body --jq '.body' | grep -E '4\.2\.1|4\.3\.1'Length of output: 92
Script:
#!/bin/bash # Description: Identify the correct repository for `@vitejs/plugin-react` and fetch release notes for versions 4.2.1 to 4.3.1. # Step 1: Search for the repository URL in package.json files. fd package.json --exec jq -r '.dependencies["@vitejs/plugin-react"]' | grep -oP 'https://github\.com/\K[^"]+' # Step 2: Fetch release notes for `@vitejs/plugin-react` from the identified repository. gh release view --repo vitejs/vite-plugin-react --json name,body --jq '.body' | grep -E '4\.2\.1|4\.3\.1'Length of output: 217
Script:
#!/bin/bash # Description: Fetch the repository URL for `@vitejs/plugin-react` from the npm registry and attempt to retrieve the changelog. # Step 1: Fetch the repository URL from the npm registry. npm info @vitejs/plugin-react repository.url # Step 2: Attempt to retrieve the changelog or release notes from the identified repository. gh repo view vitejs/vite-plugin-react --json description,homepage --jq '.description, .homepage'Length of output: 1342
Script:
#!/bin/bash # Description: Attempt to find the correct repository for `@vitejs/plugin-react` and fetch release notes. # Step 1: Use GitHub search to find the repository for `@vitejs/plugin-react`. gh repo list vitejs --json nameWithOwner,description --limit 100 | grep 'plugin-react' # Step 2: Fetch the latest release notes for the identified repository. gh release view --repo vitejs/vite-plugin-react --json name,body --jq '.name, .body'Length of output: 3081
25-25: Verify compatibility for@types/node.The update from
^20.11.16to^20.14.14is a minor version bump. Ensure that any changes in Node.js type definitions are compatible with your project's type checking.
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ccafd1f to
3c94155
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
3c94155 to
58ac8a5
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
58ac8a5 to
b5207a1
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
b5207a1 to
29a7a2f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
29a7a2f to
a5abd03
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
a5abd03 to
f2c3c5f
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f2c3c5f to
e034d03
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
e034d03 to
8f61997
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
Files selected for processing (1)
- package.json (1 hunks)
Files skipped from review due to trivial changes (1)
- package.json
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8f61997 to
64233a4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
b002c3b to
74cbaad
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
74cbaad to
a086bdd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
a086bdd to
67845cc
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
67845cc to
7e55ad1
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
7e55ad1 to
301c15d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
301c15d to
8293474
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8293474 to
7a5d96b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
7a5d96b to
6dbc301
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
6dbc301 to
d67b1c2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
d67b1c2 to
bd5eff6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
bd5eff6 to
28ca6a3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
28ca6a3 to
704b50f
Compare
|
This PR contains the following updates:
^3.2.0->^3.3.2^2.0.0->^2.2.1^20.11.16->^20.17.6^18.2.51->^18.3.12^18.2.18->^18.3.1^1.1.2->^1.3.2^4.2.1->^4.3.3^8.56.0->^8.57.1^3.2.4->^3.3.3^18.2.0->^18.3.1^18.2.0->^18.3.1^5.3.3->^5.6.3^5.0.12->^5.4.10^4.5.0->^4.5.5Release Notes
mheob/config (@mheob/prettier-config)
v3.3.2Compare Source
Patch Changes
vercel/analytics (@vercel/analytics)
v1.3.2Compare Source
What's Changed
Full Changelog: vercel/analytics@1.3.1...1.3.2
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.3.3Compare Source
React Compiler runtimeModule option removed
React Compiler was updated to accept a
targetoption andruntimeModulewas removed. vite-plugin-react will still detectruntimeModulefor backwards compatibility.When using a custom
runtimeModuleortarget !== '19', the plugin will not try to pre-optimizereact/compiler-runtimedependency.The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.
Here is the configuration to use the compiler with React 18 and correct source maps in development:
v4.3.2Compare Source
Ignore directive sourcemap error #369
eslint/eslint (eslint)
v8.57.1Compare Source
prettier/prettier (prettier)
v3.3.3Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@letdeclaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@letdeclaration syntax.Please see the following code example. The
@letdeclaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
microsoft/TypeScript (typescript)
v5.6.3Compare Source
v5.6.2Compare Source
v5.5.4: TypeScript 5.5.4Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
vitejs/vite (vite)
v5.4.10Compare Source
Please refer to CHANGELOG.md for details.
v5.4.9Compare Source
Please refer to CHANGELOG.md for details.
v5.4.8Compare Source
Please refer to CHANGELOG.md for details.
v5.4.7Compare Source
Please refer to CHANGELOG.md for details.
v5.4.6Compare Source
Please refer to CHANGELOG.md for details.
v5.4.5Compare Source
Please refer to CHANGELOG.md for details.
v5.4.4Compare Source
Please refer to CHANGELOG.md for details.
v5.4.3Compare Source
file://reference (#17909) (561b940), closes #17909v5.4.2Compare Source
renderBuiltUrlpassed to module preload (#16084) (fac3a8e), closes #16084v5.4.1Compare Source
build.modulePreload.resolveDependenciesis optimizable (#16083) (e961b31), closes #16083__vite_import_meta_env__(#17876) (e686d74), closes #17876handleHotUpdatefrom watch-package-data plugin (#17865) (e16bf1f), closes #17865v5.4.0Compare Source
globalvariable name conflict (#17809) (6aa2206), closes #17809importScriptsinjection breaking iife code (#17827) (bb4ba9f), closes #17827pmndrs/zustand (zustand)
v4.5.5Compare Source
This improves the
persistmiddleware behavior for an edge case.What's Changed
New Contributors
Full Changelog: pmndrs/zustand@v4.5.4...v4.5.5
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Berlin, 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.
This PR was generated by Mend Renovate. View the repository job log.