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
Currently, if we try to commit anything then the pre-commit git hook will automatically get triggered using Husky. Now it runs the yarn lint-staged command to check the lining rules of the code from the staged files. If we try to run the yarn lint-staged command normally after git add, it works fine. But when it runs inside an environment like husky, it will continuously produce an excess amount of the same logs, which blows up the terminal/cmd.
Additional Info
OS: Windows 10 husky Version: 8.0.0 lint-staged version: 13.0.2
Fix the excess amount of the same logs, which blows up the terminal/cmd on windows while running
lint-staged from husky
Fixes#123
Signed-off-by: Niloy Sikdar <niloysikdar30@gmail.com>
Fix the excess amount of the same logs, which blows up the terminal/cmd on windows while running
lint-staged from husky
Fixes#123
Signed-off-by: Niloy Sikdar <niloysikdar30@gmail.com>
Description:
Currently, if we try to commit anything then the
pre-commit
git hook will automatically get triggered using Husky. Now it runs theyarn lint-staged
command to check the lining rules of the code from the staged files. If we try to run theyarn lint-staged
command normally aftergit add
, it works fine. But when it runs inside an environment like husky, it will continuously produce an excess amount of the same logs, which blows up the terminal/cmd.Additional Info
OS: Windows 10
husky
Version: 8.0.0lint-staged
version: 13.0.2References:
Also, we can remove
git add -A .
from thepre-commit
hook afteryarn lint-staged
.The text was updated successfully, but these errors were encountered: