Development Tooling

This category includes tools and configurations that enforce code quality, formatting, and consistency across the development environment.

.husky

This folder sets up Git hooks using Husky, a tool for managing pre-commit and pre-push scripts.

  • It enforces code quality rules before commits and pushes, such as running lint checks (e.g., via ESLint) or formatters (e.g., Prettier) to ensure consistent code style.

  • Add or modify hooks for additional checks, like type checking with TypeScript or unit tests. This helps maintain high standards as your team grows.

.vscode

This folder standardizes VS Code settings and debugging for Next.js.

  • Standardizes the Visual Studio Code development environment with settings and extension recommendations. It ensures consistent code formatting, linting, and tooling across all team members, preventing style discrepancies.

  • Modify settings.json for project-specific formatting rules or launch.json for additional debugger configurations.

.prettierignore

This file lists files/folders ignored by Prettier during formatting.

  • Excludes generated files like dist/ or node_modules/.

  • Add project-specific exclusions for temporary or build files.

.prettierrc

This file configures Prettier for consistent code formatting.

  • Enforces style rules like indentation and quotes.

  • Adjust settings to match your team’s style guide

.eslint.config.mjs

This file configures ESLint for code quality and error checking.

  • Enforces syntax and best practices for JavaScript/TypeScript.

  • Add plugins or rules for React, accessibility, or project needs.

How is this guide ?

Last updated on