express-typescript-skeleton VS husky

I have been using TsED for a year now and I can say that so far I have not had any problems. It is very comfortable to work with this mini-framework. In addition, the creator provides very fast support and is happy to help with any problems. A few months ago I created a REST API template with hexagonal architecture using TsED.

https://github.com/borjapazr/express-typescript-skeleton

As I say in the README of the project:

This is an opinionated template. The architecture of the code base and the configuration of the different tools used has been based on best practices and personal preferences.

This template does not pretend to have the magic solution to all the problems that a developer may face when creating a REST API using Node.js. This is my contribution, after spending some time on it, to the community. It is an opinionated codebase created based on personal preferences, but also based on the application of best practices.

All criticisms and opinions are welcome, indeed I am very grateful for them. Based on them this could evolve, adapt and become something better. I am sure it will bring something to someone at some point, because even from the worst things something can be learned.

Many thanks to all of you who have taken the time to look at the project.

In this post, I will primarily discuss client-side hooks. I'll delve into three specific hooks: pre-commit, commit-msg, and pre-push. The central tool discussed will be Husky, which simplifies the configuration of Git Hooks, making it more straightforward.

Reading Biome doc I also switched from husky to lefthook.

Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.

Now, let's talk about Husky. It's a wonderful tool that enables you to run scripts on any Git hooks. We'll add a pre-commit hook to run ESLint and Stylelint checks before committing. This ensures that we don't commit code with errors.