Hook fails if it contains npm run command

[JosefBredereck]

The problem

I have discovered a new problem when using husky in combination with GitHub Desktop.

When committing any file and I have a pre-commit hook that includes any npm run script, it fails with the following message:

.husky/pre-commit: line 4:  1527 Segmentation fault npm run test-cmd 
husky - pre-commit hook exited with code 139 (error)

Because there is no more Data in the logs, I cannot find why that is.

If I just have echo "hello" in my pre-commit hook, it succeeds as expected.

Release version

Version 3.1.2 (x64)

Operating system

Windows 10

Steps to reproduce the behavior

1. npm install husky -D
2. npm pkg set scripts.prepare="husky install"
3. npm run prepare
4. npm pkg set scripts.test-cmd="echo 'hello'"
5. npx husky add .husky/pre-commit "npm test"

Log files

2022-12-02T16:55:07.684Z - info: [ui] Executing createCommit: git commit -F - (took 2.893s)
2022-12-02T16:55:07.687Z - error: [ui] git commit -F - exited with an unexpected code: 1.
stderr:
.husky/pre-commit: line 4: 290 Segmentation fault npm run test-cmd
husky - pre-commit hook exited with code 139 (error)

2022-12-02T16:55:07.688Z - info: [ui] [Timing] Action 'create commit' for 'test-commit' took 3.139s

Screenshots

No response

Additional context

No response

[AnilBairi]

This might be similar to conventional-changelog/commitlint#3485