cspell VS ESLint

CSpell is a great spell checker for code. It can be added as a source to null-ls. However, a lot of features are missing when it's used from null-ls, for instance the ability to ignore certain paths. According to this comment in a null-ls thread cspell would need its own companion plugin.

I use cspell CLI to test for spelling errors at build time so that spelling errors cannot get committed. It's very easy to automate to avoid introducing errors. I don't know of an offline library to check for grammar though.

Spell check

Are this.state.representative and this.respresentative supposed to be the same thing? First off, they are misspelled, second, not the same property. Highly recommend at least using a code spell checker cspell and VS Code - Code Spell Checker if you aren't going to use TypeScript or ESLint.

You could definitely use a spellchecker. cspell is a great programatic spellchecker that you can add to your commit or build validations to enforce that things are spelled correctly.

- cspell: https://github.com/streetsidesoftware/cspell/tree/main/packages/cspell

Also, it's response not responce. Highly recommend using the Code Spellchecker plugin for VS Code and/or the cspell cli for spellchecking.

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.

eslint is used to avoid code errors

No lint errors: The committed code does not contain any lint errors (eslint).

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

GitHub | Website

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.

ESLint

1. Lack of Static Code Analysis Static code analysis tools like TypeScript and ESLint play a crucial role in identifying and preventing bugs. TypeScript provides static typing, enhancing the robustness of the code. ESLint detects issues and enforces coding standards. The absence of these tools can significantly elevate the likelihood of bugs due to the lack of early detection and guidance provided during development.