New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⬆️ Update dependencies: code formatter packages (major) #30
base: master
Are you sure you want to change the base?
Conversation
2212f36
to
90497de
Compare
90497de
to
fc74f6c
Compare
fc74f6c
to
5c6ca59
Compare
5c6ca59
to
2284e11
Compare
0c8bd31
to
5dab2e0
Compare
5dab2e0
to
2bf8820
Compare
2bf8820
to
ffe7085
Compare
ffe7085
to
5b13b3f
Compare
5b13b3f
to
5cbf789
Compare
5cbf789
to
e73d9b2
Compare
e73d9b2
to
14762df
Compare
9e8fdd0
to
3104241
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 7142 lines exceeds the maximum allowed for the inline comments feature.
3104241
to
889be1f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 7142 lines exceeds the maximum allowed for the inline comments feature.
889be1f
to
2245609
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR diff size of 7142 lines exceeds the maximum allowed for the inline comments feature.
2a27673
to
71d5874
Compare
4847561
to
36eeebe
Compare
acc3542
to
11cba17
Compare
20c4509
to
1477a81
Compare
1477a81
to
8cccf6a
Compare
8cccf6a
to
32e4b56
Compare
52006ea
to
fca2d37
Compare
fca2d37
to
8dd6999
Compare
8dd6999
to
1e9e0bf
Compare
Code Climate has analyzed commit 1e9e0bf and detected 0 issues on this pull request. View more on Code Climate. |
This PR contains the following updates:
3.0.5
->9.0.11
9.2.5
->15.2.5
3.1.0
->4.2.0
1.18.2
->3.2.5
1.22.1
->2.10.0
Release Notes
typicode/husky (husky)
v9.0.11
Compare Source
v9.0.10
Compare Source
v9.0.9
Compare Source
v9.0.8
Compare Source
v9.0.7
Compare Source
~/.huskyrc
correctly (compatibility with v8)v9.0.6
Compare Source
v9.0.5
Compare Source
v9.0.4
Compare Source
v9.0.3
Compare Source
v9.0.2
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.0.1...v9.0.2
v9.0.1
Compare Source
Kicking off the year with an exciting update!
TLDR;
Improved user experience and a (even) smaller package size while packing in more features!
👋 By the Way
I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂
Introducing
husky init
Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.
v8
v9
Adding a New Hook
Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic
echo
command.v8
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, likely making it the smallest devDependency in your toolkit.To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for
v9
. Stay tuned 🙌Other Changes
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
What's Changed
Feats
husky -
prefix to logged global error messages by @joshbalfour in https://github.com/typicode/husky/pull/1092PATH
when command not found to improve debuggability$HUSKY=0
Fixes
/usr/bin/env sh
instead of direct path ofsh
by @skhaz in https://github.com/typicode/husky/pull/1051./husky.sh
by @hyperupcall in https://github.com/typicode/husky/pull/1104basename
/dirname
to treat$0
as an argument by @mataha in https://github.com/typicode/husky/pull/1132git.io
links by @renbaoshuo in https://github.com/typicode/husky/pull/1136Docs
npx --no-install
option withnpx --no
by @sibiraj-s in https://github.com/typicode/husky/pull/1070pnpm
installation by @MohamadKh75 in https://github.com/typicode/husky/pull/1139Chore
v7.0.4
Compare Source
No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.
v7.0.3
Compare Source
v7.0.2
Compare Source
Fix pre-commit hook in WebStorm (#1023)
v7.0.1
Compare Source
v7.0.0
Compare Source
.husky/
directory structure..husky/.gitignore
is now unnecessary and can be removed.husky-init
CLIhusky-4-to-7
CLIPlease help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!
v6.0.0
Compare Source
After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉
Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!
OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!
Breaking change
husky init
has been moved to its own package (npx husky-init
)Added
require('husky')
Migrating from husky 4
Husky 6 contains breaking changes. If you're coming from v4,
npm install husky@6
won't be enough.Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.
If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/
Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use
prepare
script instead (see usage in docs).v5.2.0
Compare Source
set
command to replace hooks (husky set .husky/pre-commit cmd
)add
command to append command (husky add .husky/pre-commit cmd
)v5.1.3
Compare Source
husky init
will detect Yarn v2 and initialize accordinglyv5.1.2
Compare Source
prepare
script instead ofpostinstall
(#890)husky init
useprepare
script (#890)v5.1.1
Compare Source
v5.1.0
Compare Source
husky init
v5.0.9
Compare Source
See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes
v5.0.8
Compare Source
v5.0.7
Compare Source
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.3
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare Source
👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.
Note about the license
Husky 5 is released under The Parity Public License.
It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️
If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.
This is only for a limited time, husky will be MIT again later.
Migrating
Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.
The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using
husky add
.v4.3.8
Compare Source
Cannot read property 'toString' of null
v4.3.7
Compare Source
v4.3.6
Compare Source
prepare-commit-msg
on windows #737v4.3.5
Compare Source
v4.3.4
Compare Source
INIT_CWD
environment variablev4.3.3
Compare Source
v4.3.2
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
.cjs
config file support #754v4.2.5
Compare Source
v4.2.4
Compare Source
cnpm
package manager #687sh
to run scripts and avoid inconsistencies #707v4.2.3
Compare Source
husky.config.js
not.huskyrc.config.js
#669v4.2.2
Compare Source
.husky.js
and.husky.config.js
update
,pre/post-receive
hooksv4.2.1
Compare Source
v4.2.0
Compare Source
<2.13.0
v4.1.0
Compare Source
v4.0.10
Compare Source
v4.0.9
Compare Source
v4.0.8
Compare Source
v4.0.7
Compare Source
winpty
(#634)v4.0.6
Compare Source
v4.0.5
Compare Source
v4.0.4
Compare Source
.eslintrc.js
(#627)v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Yarn v2
new Plug'n'Play feature (thanks to @arcanis)Cygwin
andCmdr
)dependencies
and simplify codeNode 10+
Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!
v3.1.0
Compare Source
pre-merge-commit
hook (#605)v3.0.9
Compare Source
is-ci
withci-info
#579v3.0.8
Compare Source
GIT_DIR
environment variable when hooks are runv3.0.7
Compare Source
Debug: display husky version and created at
v3.0.6
Compare Source
Debug: improve messages
okonet/lint-staged (lint-staged)
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 micromatch@4.0.7v15.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 lilconfig@3.0.0#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.v15.0.0
Compare Source
Major Changes
#1322
66b93aa
Thanks @iiroj! - Require at least Node.js 18.12.0This release drops support for Node.js 16, which is EOL after 2023-09-11.
Please upgrade your Node.js to the latest version.
Additionally, all dependencies have been updated to their latest versions.
v14.0.1
Compare Source
Bug Fixes
v14.0.0
Compare Source
Features
BREAKING CHANGES
16.14.0
.v13.3.0
Compare Source
Bug Fixes
Features
listr2@​6.6.0
(09844ca)v13.2.3
Compare Source
Bug Fixes
--diff
option implies--no-stash
(66a716d)v13.2.2
Compare Source
Bug Fixes
yaml@2.2.2
(GHSA-f9xv-q969-pqx4) (#1290) (cf691aa)v13.2.1
Compare Source
Bug Fixes
v13.2.0
Compare Source
Bug Fixes
colorette
withchalk
for better color support detection (f598725)Features
v13.1.4
Compare Source
v13.1.3
Compare Source
v13.1.2
Compare Source
Bug Fixes
v13.1.1
Compare Source
Bug Fixes
--stash
when using the--diff
option (99390c3)v13.1.0
Compare Source
Features
v13.0.4
Compare Source
Bug Fixes
v13.0.3
Compare Source
Bug Fixes
v13.0.2
Compare Source
Bug Fixes
--diff
and--diff-filter
options when checking task modifications (1a5a66a)v13.0.1
Compare Source
Bug Fixes
process.kill
when killing tasks on failure (f2c6bdd)Performance Improvements
EventsEmitter
instead ofsetInterval
for killing tasks on failure (c508b46)v13.0.0
Compare Source
Bug Fixes
execa@^6.1.0
(659c85c)yaml@^2.1.1
(2750a3d)Features
BREAKING CHANGES
lint-staged
will no longer support Node.js 12, which is EOL since 30 April 2022v12.5.0
Compare Source
Bug Fixes
--config <path>
(641d1c2)--diff
option (d4da24d)Features
--diff-filter
option for overriding list of (staged) files (753ef72)--diff
option for overriding list of (staged) files (35fcce9)v12.4.3
Compare Source
Bug Fixes
v12.4.2
Compare Source
Bug Fixes
v12.4.1
Compare Source
Bug Fixes
v12.4.0
Compare Source
Bug Fixes
parseGitZOutput
(a118817)Features
--max-arg-length
cli option (e8291b0)v12.3.8
Compare Source
Bug Fixes
v12.3.7
Compare Source
Bug Fixes
--silent
andFORCE_COLOR
settings (d327873)v12.3.6
Compare Source
Bug Fixes
v12.3.5
Compare Source
Bug Fixes
v12.3.4
Compare Source
Bug Fixes
package.json
to exports (#1059) (3395150)v12.3.3
Compare Source
Bug Fixes
v12.3.2
Compare Source
Bug Fixes
v12.3.1
Compare Source
Bug Fixes
v12.3.0
Compare Source
Features
--cwd
option for overriding task directory (62b5b83)v12.2.2
Compare Source
Bug Fixes
cwd
first (4afcda5)v12.2.1
Compare Source
Bug Fixes
v12.2.0
Compare Source
Bug Fixes
Features
v12.1.7
Compare Source
Bug Fixes
v12.1.6
Compare Source
Bug Fixes
v12.1.5
Compare Source
Bug Fixes
--debug
option enables debug mode (5cceeb6)v12.1.4
Compare Source
Bug Fixes
v12.1.3
[Compare Source](https://togithub.com/okon
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.
This PR has been generated by Mend Renovate. View repository job log here.