Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • app app
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Ludo Pets
  • appapp
  • Merge requests
  • !4

Merged
Created Mar 21, 2025 by Gustavo Pretto Scholze@gustavo.scholzeOwner

Setup of ESLint, Prettier and Husky

  • Overview 0
  • Commits 2
  • Changes 24

Setup of the ESLint, Prettier and Husky for better code formatting.

Environment configuration

All the installation and setup of the proposed tools are described below.

  • ESLint
  • Prettier
  • EditorConfig

Why are we using it?

Husky is being used as a pre-commit hook tool. Currently, whenever the developer commits, Husky will run the commands:

$ npx prettier --check . --write
$ npx eslint

If there are no warnings from ESLint, your terminal will output the message below. Else, it will output the sections with the wrong formatting. image

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/02-configuring-boilerplate