-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
silent npm run #26
Comments
Originally, it was to make hooks output less verbose and more readable:
vs
Though, I agree that it hides things. But if you need to debug stuff, you can run |
I thought about it sometime, and ended up with thought that its nice to hide if everything is okay, but if it failed, then it will be better to show the error message. what do you think? |
+1 |
@typicode any thoughts? |
Sorry, forgot to reply. I'm currently on vacation with just my phone, will make a better/more detailed answer when I get back :) |
I found this behaviour confusing, so it would be great to add some note about this in the readme. |
Sorry for the delay. I've removed the Thank you all for the feedbacks :) |
@typicode just saying "thanks for husky and your time" again =) |
@typicode actually it would be great if the silent (or other) flag could be used as an option. What do you think? |
I prefer to avoid adding options to keep it simple and I'm kind of satisfied with husky not being |
I think optional silent would be helpful. When I am using git hooks for linting source code, those lint errors would be enough. |
why did you choose run npm scripts in silent? usually its hiding some problems
husky will fail, and you will have no idea what is a problem
The text was updated successfully, but these errors were encountered: