chore(deps): update non-major dependencies #325
+291
−345
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
16.0.1
->16.1.0
18.3.12
->18.3.16
18.3.1
->18.3.5
8.16.0
->8.18.0
8.16.0
->8.18.0
14.2.18
->14.2.20
5.0.0
->5.1.0
0.4.14
->0.4.16
14.2.18
->14.2.20
3.4.1
->3.4.2
6.0.2
->6.0.3
2.1.6
->2.1.8
Release Notes
testing-library/react-testing-library (@testing-library/react)
v16.1.0
Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.18.0
Compare Source
🚀 Features
🩹 Fixes
toString()
declarations are present for a type (#10432)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.17.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.18.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.17.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.
vercel/next.js (eslint-config-next)
v14.2.20
Compare Source
v14.2.19
Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner and @ijjk for helping!
facebook/react (eslint-plugin-react-hooks)
v5.1.0
Compare Source
ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)
v0.4.16
Compare Source
Fix CJS/ESM interop issue. Sorry everyone for the trouble.
v0.4.15
Compare Source
Add support for custom HOCs (#60)
By default, the rule only knows that
memo
&forwardRef
function calls with return a React component. With this option, you can also allow extra function names like Mobx observer to make this code valid:Thanks @HorusGoul!
Add recommended config and simple types (#67)
You can now add the recommended config to your ESLint config like this:
To follow ESLint recommandations, the rule is added with the
error
severity.Some simple types ensure that people typecheking their config won't need
@ts-expect-error
anymore.Bump ESLint peer dependency to 8.40
This was actually done by mistake in the previous release when moving from a deprecated API to a new one.
Given that ESLint 8 is officialy end-of-life and the only report (#56) didn't get likes, I'm going forward and documenting the expected minimum version from ESLin in the package JSON so that people can get warning from their package manager.
vercel/next.js (next)
v14.2.20
Compare Source
v14.2.19
Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner and @ijjk for helping!
prettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
vitejs/vite (vite)
v6.0.3
Compare Source
ModuleRunnerTransport#invoke
more explicit (#18851) (a75fc31), closes #18851environments.ssr.resolve
with rootssr
config (#18857) (3104331), closes #18857vitest-dev/vitest (vitest)
v2.1.8
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.1.7
Compare Source
🐞 Bug Fixes
pnpm.overrides
or yarn resolutions to override thevite
version in thevitest
package - the APIs are compatible.View changes on GitHub
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" in timezone America/New_York, 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.