You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
Please describe your issue and provide some context:
Terminal or GUI client (PowerShell, Git Bash, GitHub Desktop, ...)
If applicable, content of the failing hook
If possible, minimal steps to reproduce the issue
Thank you!
I wanna check my code with eslint + lint-staged, but my CI node image version is lower than 18, so should I find a way to avoid to install husky in CI ? Or just delete husky in package.json ?
Can I have better way than telling everyone to install husky in localhost to solve this ?
Thanks to what you have done in this repo
What I met :
error husky@9.0.10: The engine "node" is incompatible with this module. Expected version ">=18". Got "16.19.0"
The text was updated successfully, but these errors were encountered:
cai-zhuo
changed the title
Yarn add husky failed due to node version is less than 18, How can I skip installing in CI
Yarn add husky failed due to node version is lower than 18, How can I skip installing in CI
Feb 6, 2024
We are bypassing husky install in circleci using below code, thought it might help you as well "prepare": "is-ci || husky install"
above script needs to be added in package.json
is-ci is very simple npm module https://www.npmjs.com/package/is-ci
Troubleshoot
https://typicode.github.io/husky/troubleshoot.html
If you're migrating from husky 4, see:
https://typicode.github.io/husky/migrate-from-v4.html
Context
Please describe your issue and provide some context:
Thank you!
I wanna check my code with eslint + lint-staged, but my CI node image version is lower than 18, so should I find a way to avoid to install husky in CI ? Or just delete husky in package.json ?
Can I have better way than telling everyone to install husky in localhost to solve this ?
Thanks to what you have done in this repo
What I met :
The text was updated successfully, but these errors were encountered: