chore(husky): configure pre-commit hooks for code linting and formatting #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Integrating Husky, Commitlint, and Prettier into project brings several significant improvements:
Consistent Code Style: Prettier ensures that all code follows a consistent style, making it more readable and easier to maintain.
Quality Assurance: Husky, with pre-commit hooks, ensures that tests, linters, and formatters run automatically before each commit, helping to catch issues early.
Commit Message Standardization: Commitlint enforces a conventional commit message format, improving the readability of commit history and aiding in automated version control and changelog generation.
Overall, these tools enhance code quality, maintainability, and collaboration efficiency within the project.