Terminal is being exploded with repeated log outputs

@akamfoad Describes and show this issue really good below. But there is more to it. When it gets repeated like shown below TaskManager show there is a lot of node.js instances spun up slowing down the computer. It affects the computer so much that it actully makes js-tests (jest) to timeout.

This issue really needs to be addressed otherwise I think this will affect usage. My colleagues are already using the --no-verify flag when commiting.

Please let me know if there is anything I can provide to ease the finding of a solution!

OS: Windows Shell: git bash Git version: 2.37.3 packagemanager: npm

Hi, I have a similar issue but in my case the terminal is being exploded with repeated log output.

OS: Windows
Shell: PowerShell 7.2.6
Git Version: 2.37.1.windows.1

running

yarn lint-staged

Through git hooks (added with husky):

https://user-images.githubusercontent.com/41629832/188649709-a61d2579-319a-487b-b2cf-abb89b75cace.mp4

Directly running the command:

https://user-images.githubusercontent.com/41629832/188650212-0fa8b4ea-bc04-43f7-9c88-1d68045e96a4.mp4

_Originally posted by @akamfoad in https://github.com/typicode/husky/issues/968#issuecomment-1238185342_

[gillesdalle]

Duplicate bug : https://github.com/okonet/lint-staged/issues/1164 Found a soluition in https://github.com/typicode/husky/issues/968#issuecomment-1176848345 Add exec >/dev/tty 2>&1 before your command lines in pre-commit file.

[J4v4Scr1pt]

Duplicate bug : okonet/lint-staged#1164 Found a soluition in #968 (comment) Add exec >/dev/tty 2>&1 before your command lines in pre-commit file.

Interesting, will test! Thx m8!

Edit: This does solve the issue. Thanks man for finding this! 🐱‍💻

EditTwo: Well it solved it for me but my colleagues got error instead and we had to remove it… back to square one.