Can we make Husky an optional install?

[openspaceranger]

What do you want and why?

I was unable to fix the "command not found" problem with Husky. Until I uninstalled it, I was unable to make a git commit.

Possible implementation(s)

I'm not sure if it's possible without removing it, but it would it nice if it didn't interfere with anything for people who are not interested in it.

Additional context

As a new blitz user, Husky and node-gyp gave me headaches. A lot of people would have simply just given up and used Nextjs instead. I strongly feel that it hinders new adopters of Blitz.

[tordans]

Also ping #3981 (comment) which was closed in a recent "close all old issues"-run.

[tordans]

Personally, I recommend changing pre-commit to pre-push which still gives the security to not push without running checks but allows for WIP commits without extra work (like git commit --no-verify).

[siddhsuresh]

sorry about the experience @openspaceranger, we are addressing the node-gyp issue currently and will be fixed in the next version.

Regarding husky, we will need to discuss it, since I see that there were plans to remove it in its entirety from the new template.

Another option that comes to mind, would be to add it as step in the onboarding generator and the user can choose to include these optional nice-to-have configurations.