-
Notifications
You must be signed in to change notification settings - Fork 119
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
chore: update husky package for web #1355
Conversation
Hey @orvn! Sorry I've totally neglected this PR till now 🤦♂️ Do you think this is safe to merge? |
getTokens() | ||
}, []); | ||
getTokens(); | ||
}, [getTokens]); |
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.
This was the only linting violation I had to manually resolve, the rest were all minor things it seems. I don't think this breaks anything here?
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.
No, not seeing any issues here either
…website package.
be63e80
to
a7784a9
Compare
…e-commit-for-website
This reverts commit 6c29ae0.
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.
I tested the pre-commit hooks in a few different contexts and all seems well! Upon merging main
, I needed to rebuild the repo's base package-lock.json
…e/update-husky-pre-commit-for-website
Cool, I'll merge this now, thanks @orvn! |
Had issues committing code as pre-commit hooks could not find the husky config.
Huskys latest version no longer auto installs to align with npms best practices , so thought it best to use the latest version of the package.
So In this PR, to get things working I have:
.husky/pre-commit
for website package