Fix: Migrate husky hooks to v9 format #701
Merged
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.
Because
The current installed Husky version is v9 but
package.json
contains the old v4 way of setting hooks. This doesn't work in v9 solint-staged
was never being run pre-commit. While we already have GH workflows for the same actions, it helps to have this at the local level too and reduce "appease linter/formatter" commits. Belts and braces.This PR
prepare
npm script to ensurenpm install
also initialises husky (its setup files include a.gitignore
that ignores themselves) https://typicode.github.io/husky/how-to.html#manual-setuplint-staged
tasks for different file types to also include PrettierIssue
N/A
Additional Information
Example trying to commit a single change to
index.js
that includes alet foo;
somewhere.Current behaviour:
With PR fix:
Pull Request Requirements
location of change: brief description of change
format, e.g.Callbacks command: Update verbiage
Because
section summarizes the reason for this PRThis PR
section has a bullet point list describing the changes in this PRIssue
section