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](https://typicode.github.io/husky/#/?id=used-by) 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](https://github.com/sponsors/typicode) or [Open Collective](https://opencollective.com/husky). Thank you!_
Breaking change
- `husky init` has been moved to its own package (`npx husky-init`)
Added
- Programmatically use husky: `require('husky')`
- TypeScript definitions
Migrating from husky 4
Husky 6 contains breaking changes. If you're coming from v4, `npm install husky6` won't be enough.
__Recommended:__ see [husky-4-to-6](https://typicode.github.io/husky/#/?id=husky-4-to-6-cli) CLI to automatically migrate your config. There's also a dedicated section in the [docs](https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v6).
__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](https://docs.npmjs.com/cli/v7/using-npm/scripts#best-practices) and [Yarn](https://yarnpkg.com/advanced/lifecycle-scripts#a-note-about-postinstall) best practices regarding autoinstall.__ It's recommended to use `prepare` script instead (see [usage](https://typicode.github.io/husky/#/?id=usage) in docs).