re: JS Project Setup: Code Quality is simple when you don't have to do anything VIEW POST

TOP OF THREAD FULL DISCUSSION
re: There's nothing wrong with normal git hooks if you prefer to set them up the original way, or if you find it easier to do it that way. Husky just h...
 

Uh, another leftpad, got it, thanks.

This is an unfair jab and also unnecessarily condescending.

Husky provides many benefits over plain git hooks. One, being able to manage the hooks from your project.json. This makes them visible to anyone viewing the source. They are also source controlled.

Hooks are local to any given Git repository, and they are not copied over to the new repository when you run git clone

This has an important impact when configuring hooks for a team of developers. First, you need to find a way to make sure hooks stay up-to-date amongst your team members

Sloan, the sloth mascot Comment marked as low quality/non-constructive by the community View code of conduct

being able to manage the hooks from your project.json

I have a gut feeling hooks were made repo-local on purpose. I might come up with a dozen examples why, but it would be too large to fit in the margin.

This is perfect example of abusing the tool of choice (git) because we are too stupid to understand how to use it properly.

This is perfect example of abusing the tool of choice (git) because we are too stupid to understand how to use it properly.

Agree to disagree.

code of conduct - report abuse