Ajith Kumar P M

As the project grows larger it's critical for the whole team to follow certain code quality and security standards. One way to ensure that is by using "git hooks".

Git hooks are scripts that run automatically every time a particular event occurs in a Git repository.

Numerous git hook managers are available for Node.js. Husky, pre-commit, and Lefthook are a few examples of such tools. We opted for Lefthook for this tutorial due to its capability to execute scripts concurrently and its simplicity.So let's start!Before each commit(pre-commit) we need to ensure the following.

No credentials leak: To ensure no secrets are accidentally exposed in the source.
No lint errors: The committed code does not contain any lint errors (eslint).
No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).
No type errors: There shouldn't be any typescript errors.

And on each pre-push we need to ensure the following

No vulnerable packages: npm audit or pnpm audit --audit-level high
Standardized branch-names: we can usevalidate-branch-name

Apart from these we also need to enforce standards for all our commit messages(commit-lint).

GitLeaks

install gitleaks in your machine gitleaksadd the following changes to your package.json

Eslint

install and configure eslint with

add the following changes to your package.json

Typecheck

Prettier for code formatting

Package.json

Branch name validations

Package.json

Commit lint for standardized commit messages

create the file commitlint.config.js at the root

create the file .lefthook/commit-msg/commitlint.sh

bash

Lefthook as githooks manager

yml

package.json

Run lefthook install and try making your first commit.

As the project grows larger it's critical for the whole team to follow certain code quality and security standards. One way to ensure that is by using "git hooks".

Git hooks are scripts that run automatically every time a particular event occurs in a Git repository.

No credentials leak: To ensure no secrets are accidentally exposed in the source.
No lint errors: The committed code does not contain any lint errors (eslint).
No formatting inconsistencies: The committed code should follow the organization's code formatting standards(prettier or pretty-quick).
No type errors: There shouldn't be any typescript errors.

And on each pre-push we need to ensure the following

No vulnerable packages: npm audit or pnpm audit --audit-level high
Standardized branch-names: we can usevalidate-branch-name

Apart from these we also need to enforce standards for all our commit messages(commit-lint).

GitLeaks

install gitleaks in your machine gitleaksadd the following changes to your package.json

Eslint

install and configure eslint with

add the following changes to your package.json

Typecheck

Prettier for code formatting

Package.json

Branch name validations

Package.json

Commit lint for standardized commit messages

create the file commitlint.config.js at the root

create the file .lefthook/commit-msg/commitlint.sh

bash

Lefthook as githooks manager

yml

package.json

Run lefthook install and try making your first commit.

How to Add Pre/post-Commit Hooks to Your Node.js Project

Ajith Kumar P M

GitLeaks

Eslint

Typecheck

Prettier for code formatting

Branch name validations

Commit lint for standardized commit messages

Lefthook as githooks manager

How to Add Pre/post-Commit Hooks to Your Node.js Project

Ajith Kumar P M

GitLeaks

Eslint

Typecheck

Prettier for code formatting

Branch name validations

Commit lint for standardized commit messages

Lefthook as githooks manager