I'm happy to announce the release of husky 5 🎉 🐺 woof!
During the past years, husky has grown in complexity. With this version, I wanted to go bac...
For further actions, you may consider blocking this person and/or reporting abuse
Like others, I have to say
husky@4
works very nice and easy to use, but v5 is much more difficult to understand and config.I think you should balance between performance and easy-to-use.
I can't wait to use v6 now. 🤪
I want to be clear that I 100% support the move to the new license and the financial support that hopefully brings to you.
husky
is a wonderful tool and has saved my bacon many times.That said, did you consider not releasing it with the
latest
tag on NPM and having something likeoss
and/orsponsored
tags instead for v5 and keepinglatest
pointing at v4? I wonder how many folks have runnpm i -D husky
or had dependabot come through and bumped their version and not realised they are up for sponsorship now.Exactly. Broke plenty of projects. Plenty of open source projects have a commit of just rolling/reverting back husky to v4.
I totally agree. Having hooks configured in package.json was very straightforward.
Technically it was zero extra files config (as package.json stays in project anyway).
Now it's totally not clear to me where config should live, and polluting repo with extra config files doesn't feel good.
Yeah, the ease of setting up hooks with husky+lint staged is a nightmare now when they used to be a breeze to set up.
I'm in the same boat, looking for an alternative for the time being. Actually, I've never had any problems about husky so far, their configuration interface was superb but now it tries to solve a problem that doesn't exist.
I went back to v4 once I have discover that
postinstall
=>prepare
v5.1.2Roll back to v4
thanks sharing your work with the world!
Withhout writing precommit file to .git/hooks, how new husky now works?