chore(deps): update all minor and patch dependencies #276
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:
6.0.1
->6.6.2
14.0.0
->14.3.1
14.4.3
->14.5.2
16.1.1
->16.1.3
29.5.12
->29.5.13
^18.2.20
->^18.3.11
^18.2.7
->^18.3.1
3.3.2
->3.7.1
16.3.1
->16.4.5
11.1.1
->11.2.0
10.3.3
->10.4.5
9.0.11
->9.1.6
15.0.0
->15.2.10
2.29.4
->2.30.1
3.0.3
->3.3.3
1.67.0
->1.80.3
10.9.1
->10.9.2
5.2.2
->5.6.3
3.5.3
->3.9.1
3.4.0
->3.5.2
Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.6.2
Compare Source
Bug Fixes
v6.6.1
Compare Source
v6.6.0
Compare Source
v6.5.0
Compare Source
v6.4.8
Compare Source
v6.4.7
Compare Source
v6.4.6
Compare Source
Bug Fixes
v6.4.5
Compare Source
Bug Fixes
v6.4.4
Compare Source
v6.4.3
Compare Source
v6.4.2
Compare Source
Bug Fixes
v6.4.1
Compare Source
Bug Fixes
TestingLibraryMatchers
from "./matchers" (#576) (dd1c4dd)v6.4.0
Compare Source
Features
v6.3.0
Compare Source
Features
v6.2.1
Compare Source
Bug Fixes
v6.2.0
Compare Source
Features
v6.1.6
Compare Source
Bug Fixes
v6.1.5
Compare Source
Bug Fixes
v6.1.4
Compare Source
Bug Fixes
@adobe/css-tools
to4.3.1
to address vulnerability (#532) (44f1eab)v6.1.3
Compare Source
Bug Fixes
v6.1.2
Compare Source
Bug Fixes
v6.1.1
Compare Source
Bug Fixes
v6.1.0
Compare Source
Features
testing-library/react-testing-library (@testing-library/react)
v14.3.1
Compare Source
Bug Fixes
v14.3.0
Compare Source
v14.2.2
Compare Source
v14.2.1
Compare Source
Bug Fixes
v14.2.0
Compare Source
Features
reactStrictMode
option to enable strict mode render (#1241) (0880eba)v14.1.2
Compare Source
Bug Fixes
v14.1.1
Compare Source
Bug Fixes
v14.1.0
Compare Source
Features
testing-library/user-event (@testing-library/user-event)
v14.5.2
Compare Source
Bug Fixes
v14.5.1
Compare Source
Bug Fixes
v14.5.0
Compare Source
Bug Fixes
Features
tsconfig/bases (@tsconfig/node16)
v16.1.3
Compare Source
v16.1.2
Compare Source
vitejs/vite-plugin-react-swc (@vitejs/plugin-react-swc)
v3.7.1
Compare Source
Ignore directive sourcemap error #231
v3.7.0
Compare Source
Support HMR for class components
This is a long overdue and should fix some issues people had with HMR when migrating from CRA.
v3.6.0
Compare Source
Add parserConfig option
This will unlock to use the plugin in some use cases where the original source code is not in TS. Using this option to keep using JSX inside
.js
files is highly discouraged and can be removed in any future version.v3.5.0
Compare Source
Update peer dependency range to target Vite 5
There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.
Align jsx runtime for optimized dependencies
This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have
React
in the scope.Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.
v3.4.1
Compare Source
Add support for
.mts
(fixes #161)Using CJS in source code will not work in Vite (and will never be supported), so this is better to only use
.ts
.But to better align with Vite core defaults,
.mts
extension will now be processed like.ts
. This maybe reverted in a future major.v3.4.0
Compare Source
devTarget
option (fixes #141)config.server.hmr === false
instead ofprocess.env.TEST
motdotla/dotenv (dotenv)
v16.4.5
Compare Source
Changed
path
option. return to historical behavior: do not attempt to auto find.env
ifpath
set. (regression was introduced in16.4.3
) #814v16.4.4
Compare Source
Changed
?.
with old school&&
(fixing node 12 failures) #812v16.4.3
Compare Source
Changed
options.path
#805v16.4.2
Compare Source
Changed
dotenvx.com
v16.4.1
Compare Source
path
option #797v16.4.0
Compare Source
error.code
to error messages around.env.vault
decryption handling #795.env.vault
file when filename(s) passed as an array #784v16.3.2
Compare Source
Added
Changed
populate
#792jprichardson/node-fs-extra (fs-extra)
v11.2.0
Compare Source
async
/await
(#1020)isaacs/node-glob (glob)
v10.4.5
Compare Source
v10.4.4
Compare Source
v10.4.3
Compare Source
v10.4.2
Compare Source
v10.4.1
Compare Source
v10.4.0
Compare Source
v10.3.16
Compare Source
v10.3.15
Compare Source
v10.3.14
Compare Source
v10.3.13
Compare Source
v10.3.12
Compare Source
v10.3.11
Compare Source
v10.3.10
Compare Source
v10.3.9
Compare Source
v10.3.8
Compare Source
v10.3.7
Compare Source
v10.3.6
Compare Source
v10.3.5
Compare Source
v10.3.4
Compare Source
typicode/husky (husky)
v9.1.6
Compare Source
v9.1.5
Compare Source
v9.1.4
Compare Source
v9.1.3
Compare Source
PATH
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
Super saiyan
goddog! It's over 9.0.0!There's a bug with this release which prevents the deprecation notice to appear and requires to remove
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
(which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.What's new
You can now run package commands directly, no need for
npx
or equivalents.It makes writing hooks more intuitive and is also slightly faster 🐺⚡️
A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.
For more advanced use cases, see lint-staged.
Fixes
bunx husky init
commandDeprecations
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
from your hooks~/.huskyrc
to.config/husky/init.sh
Support for these will be removed in v10, notices have been added.
Friendly reminder
If Git hooks don't fit your workflow, you can disable Husky globally. Just add
export HUSKY=0
to.config/husky/init.sh
.I've seen some confusion about this on X, so just a heads-up!
Sponsoring
Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.
Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉
lint-staged/lint-staged (lint-staged)
v15.2.10
Compare Source
Patch Changes
e3f283b
Thanks @iiroj! - Update minor dependencies, includingmicromatch@~4.0.8
.v15.2.9
Compare Source
Patch Changes
b69ce2d
Thanks @iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected
.v15.2.8
Compare Source
Patch Changes
f0480f0
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version switched the--show-toplevel
flag with--show-cdup
, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process
. The new flag returns a path relative to the working directory, avoiding the issue.The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
v15.2.7
Compare Source
Patch Changes
a51be80
Thanks @iiroj! - In the previous version the nativegit rev-parse --show-toplevel
command was taken into use for resolving the current git repo root. This version drops the--path-format=absolute
option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggit
to the latest version.v15.2.6
Compare Source
Patch Changes
119adb2
Thanks @iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.v15.2.5
Compare Source
Patch Changes
#1424
31a1f95
Thanks @iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.#1423
91abea0
Thanks @iiroj! - Improve error logging when failing to read or parse a configuration file#1424
ee43f15
Thanks @iiroj! - Upgrade [email protected]v15.2.4
Compare Source
Patch Changes
4f4537a
Thanks @iiroj! - Fix release issue with previous version; update dependenciesv15.2.2
Compare Source
Patch Changes
fdcdad4
Thanks @iiroj! - Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.v15.2.1
Compare Source
Patch Changes
e4023f6
Thanks @iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.v15.2.0
Compare Source
Minor Changes
f3378be
Thanks @iiroj! - Using the--no-stash
flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag--no-hide-partially-staged
that is automatically enabled when--no-stash
is used.Patch Changes
#1362
17bc480
Thanks @antonk52! - update [email protected]#1368
7c55ca9
Thanks @iiroj! - Update most dependencies#1368
777d4e9
Thanks @iiroj! - To improve performance, only uselilconfig
when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.#1373
85eb0dd
Thanks @iiroj! - When determining git directory, usefs.realpath()
only for symlinks. It looks likefs.realpath()
changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0
Compare Source
Minor Changes
0423311
Thanks @danielbayley! - Add support for loading configuration frompackage.yaml
andpackage.yml
files, supported bypnpm
.Patch Changes
105d901
Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2
Compare Source
Patch Changes
8e82364
Thanks @iiroj! - Update dependencies, including listr2@7.0.2 to fix an upstream issue affecting lint-staged.v15.0.1
Compare Source
Patch Changes
d2e6f8b
Thanks @louneskmt! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead.moment/moment (moment)
v2.30.1
Compare Source
a lot of TS code.
v2.30.0
Compare Source
prettier/prettier (prettier)
v3.3.3
Compare 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
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
@let
declaration 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 A
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 is behind base branch, 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.