All 15 Git & Project Management questions
More in Git & Project Management
How would you set up branch protection rules and required status checks for a Node.js repository to prevent broken code from being merged? What is the difference between npm, Yarn, and pnpm as Node.js package managers, and what specific advantage does pnpm offer regarding disk space? What is a pull request template, and how does it help standardize code review in a Node.js team's Git workflow? What is the purpose of an npm 'scripts' section in package.json, and how do custom scripts standardize common project tasks across a team? How would you structure conventional commit messages in a Node.js project, and how do they enable automated changelog generation? How would you use Git bisect to find the specific commit that introduced a regression in a Node.js application's behavior? How would you configure a Node.js project's package.json to support both being used as a library (imported by others) and having its own development scripts, distinguishing dependencies from devDependencies correctly? How would you use Git tags in combination with a CI/CD pipeline to trigger a production release of a Node.js application? How would you handle a Node.js project's dependency vulnerabilities reported by 'npm audit' as part of a CI/CD pipeline?
Advertisement
Back to results for “Testing with Jest”
Node.js › Git & Project Management

How would you use Git hooks (like a pre-commit hook via Husky) to enforce code quality checks before code is committed in a Node.js project?

Advanced

Answer

Git hooks are scripts that run automatically at specific points in the Git workflow (before a commit, before a push) -- Husky is a popular tool that makes configuring these hooks straightforward within a Node.js project's package.json, commonly used to run a linter, formatter, or a fast subset of tests against only the staged files before allowing a commit to proceed, catching basic issues locally before they ever reach a shared branch or CI.
// package.json
"husky": { "hooks": { "pre-commit": "lint-staged" } },
"lint-staged": { "*.js": ["eslint --fix", "prettier --write"] }

// This automatically lints and formats only the files being committed,
// before the commit is actually allowed to complete
Real-world example A team configures Husky and lint-staged to automatically run ESLint and Prettier on only the files being committed, catching style violations and simple bugs locally before a developer even pushes, rather than discovering them later in a CI pipeline or code review.

Common follow-ups: Why does lint-staged specifically run checks only against staged files rather than the entire codebase on every commit?;What's the risk of a pre-commit hook that takes too long to run, and how do teams balance thoroughness against developer friction?

Testing with Jest Mocha & the Node Test Runner;CI/CD Publishing & Deployment
All 15 Git & Project Management questions