Open ezeamin opened 3 months ago
Hi!
For existing hooks, it's better to follow the 'How to migrate' section from https://github.com/typicode/husky/releases/tag/v9.0.1
I'll update docs to make that clearer.
Hello @typicode and @ezeamin,
we use the script prepare
for more than just husky
. I think it is more comfortable to leave it as it is.
@typicode I created a pull request #1407 to fix this issue, please test and check.
At least there should be a condition to check if prepare script has any commands in it or not If there is a command then this husky
command should be appended.
Like this
- 14 ;(o.scripts ||= {}).prepare = 'husky'
+ 14 ;(o.scripts ||= {}).prepare = '' === (o.scripts ||= {}).prepare ? 'husky' : (o.scripts ||= {}).prepare + ' && husky'
Raised the PR for the mentioned solution please check it out.
At least there should be a condition to check if prepare script has any commands in it or not If there is a command then this
husky
command should be appended.Like this
- 14 ;(o.scripts ||= {}).prepare = 'husky' + 14 ;(o.scripts ||= {}).prepare = '' === (o.scripts ||= {}).prepare ? 'husky' : (o.scripts ||= {}).prepare + ' && husky'
Raised the PR for the mentioned solution please check it out.
Hi @SH4LIN,
Maybe we experienced the same mistake. According to typicode's reply in PR #1407, the custom scripts should be placed in .husky/
, but not in .husky/_/
. The .husky/_/
directory is managed by husky itself.
Hope this could make sense for you.
Context
Hi! Husky is working great so far, thanks for your time! But, when I run
pnpm exec husky init
, following the docs, it installs the hooks but also replaces myprepare
script withprepare: husky
. I understand the purpose of this behaviour, but if I have aprepare
script already, it should't replace it with its own script.It also replaces my repo pre-commit file inside of
/husky
with a default one that doespnpm test
. This is undesired behavior, because I already had a configuration written for the pre-commit hook.