zthxxx / react-dev-inspector

jump to local IDE code directly from browser React component by just a simple click
https://react-dev-inspector.zthxxx.me
MIT License
1.15k stars 68 forks source link

chore(deps): update dependency husky to v7 #86

Closed zthxxx closed 3 years ago

zthxxx commented 3 years ago

This PR contains the following updates:

Package Type Update Change
husky (source) devDependencies major 4.3.8 -> 7.0.0

Release Notes

typicode/husky ### [`v7.0.0`](https://togithub.com/typicode/husky/releases/v7.0.0) [Compare Source](https://togithub.com/typicode/husky/compare/v6.0.0...v7.0.0) - Improve `.husky/` directory structure. **`.husky/.gitignore` is now unnecessary and can be removed**. - Improve error output (shorter) - Update [`husky-init`](https://togithub.com/typicode/husky-init) CLI - Update [`husky-4-to-7`](https://togithub.com/typicode/husky-4-to-7) CLI - Drop Node 10 support *Please help me develop and release OSS projects :heart: on [GitHub Sponsors](https://togithub.com/sponsors/typicode) or [Open Collective](https://opencollective.com/husky). Thank you for your support!* ### [`v6.0.0`](https://togithub.com/typicode/husky/releases/v6.0.0) [Compare Source](https://togithub.com/typicode/husky/compare/v5.2.0...v6.0.0) 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://togithub.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 husky@6` 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). ### [`v5.2.0`](https://togithub.com/typicode/husky/releases/v5.2.0) [Compare Source](https://togithub.com/typicode/husky/compare/v5.1.3...v5.2.0) - Add `set` command to replace hooks (`husky set .husky/pre-commit cmd`) - Update `add` command to append command (`husky add .husky/pre-commit cmd`) - Improve error messages ### [`v5.1.3`](https://togithub.com/typicode/husky/releases/v5.1.3) [Compare Source](https://togithub.com/typicode/husky/compare/v5.1.2...v5.1.3) - docs: add specific Yarn v2 install/uninstall instructions - cli: `husky init` will detect Yarn v2 and initialize accordingly ### [`v5.1.2`](https://togithub.com/typicode/husky/releases/v5.1.2) [Compare Source](https://togithub.com/typicode/husky/compare/v5.1.1...v5.1.2) - docs: recommend `prepare` script instead of `postinstall` ([#​890](https://togithub.com/typicode/husky/issues/890)) - cli: `husky init` use `prepare` script ([#​890](https://togithub.com/typicode/husky/issues/890)) ### [`v5.1.1`](https://togithub.com/typicode/husky/releases/v5.1.1) [Compare Source](https://togithub.com/typicode/husky/compare/v5.1.0...v5.1.1) - style(shell): add trailing newlines ([#​870](https://togithub.com/typicode/husky/issues/870)) - fix(init): update package.json postinstall ### [`v5.1.0`](https://togithub.com/typicode/husky/releases/v5.1.0) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.9...v5.1.0) - Add `husky init` ### [`v5.0.9`](https://togithub.com/typicode/husky/releases/v5.0.9) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.8...v5.0.9) - fix(install): do not fail if not inside a Git directory (closes [#​851](https://togithub.com/typicode/husky/issues/851)) See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes ### [`v5.0.8`](https://togithub.com/typicode/husky/releases/v5.0.8) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.7...v5.0.8) - fix(install): better handle Git <2.9 ([#​846](https://togithub.com/typicode/husky/issues/846)) closes [#​844](https://togithub.com/typicode/husky/issues/844) ### [`v5.0.7`](https://togithub.com/typicode/husky/releases/v5.0.7) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.6...v5.0.7) - fix(shell): double quote params ([#​824](https://togithub.com/typicode/husky/issues/824)) ### [`v5.0.6`](https://togithub.com/typicode/husky/releases/v5.0.6) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.5...v5.0.6) - Remove unused files ### [`v5.0.5`](https://togithub.com/typicode/husky/releases/v5.0.5) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.4...v5.0.5) - Fix custom directory support [#​827](https://togithub.com/typicode/husky/issues/827) ### [`v5.0.4`](https://togithub.com/typicode/husky/compare/v5.0.3...v5.0.4) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.3...v5.0.4) ### [`v5.0.3`](https://togithub.com/typicode/husky/compare/v5.0.2...v5.0.3) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.2...v5.0.3) ### [`v5.0.2`](https://togithub.com/typicode/husky/compare/v5.0.1...v5.0.2) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.1...v5.0.2) ### [`v5.0.1`](https://togithub.com/typicode/husky/compare/v5.0.0...v5.0.1) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.0...v5.0.1) ### [`v5.0.0`](https://togithub.com/typicode/husky/releases/v5.0.0) [Compare Source](https://togithub.com/typicode/husky/compare/v4.3.8...v5.0.0) 👉 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`.

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Renovate Bot.

vercel[bot] commented 3 years ago

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/zthxxx/react-dev-inspector/CtapecrfARSkzUABsa1ijiFNYSVf
✅ Preview: Failed

zthxxx commented 3 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 7.x releases. However, if you upgrade to 7.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.