Application Security Testing: An Integral Part of DevOps
Linting is the process of checking the source code for programmatic and stylistic errors. A Linter is an automated tool that runs on static code to find formatting discrepancy, non-adherence to coding standards and conventions, and find logical errors in your program. Running a Linter (static code analyzer) over your source code improves code quality, helps to ensure that source code is legible, readable, less polluted and easier to maintain. Linters are also useful for code formatting and adhering to language-specific best practices.
Figure 1: The JS Lint logo
Figure 2: The ESLint logo
A developer can integrate ESLint extensions into their VS Code editor. This extension uses the ESLint library installed in the opened workspace folder.
Figure 3: The JSHint logo
JSCS's primary goal is to codify style guides for easy verification and fixing. To use JSCS, you have install it using npm. It can be used directly from your application code and also can be configure to use specific options.
Figure 4: The JSCS logo
5. Standard JS
Figure 5: The Standard JS logo
Finally, if you ask about my choice of these five, ESLint is my preference. For VS code developers, ESLint can be configured easily. JSHint is my second choice. If you don't need the advanced linting features, JSHint catches a good number of issues once it's properly configured. JSCS is a good choice if you only want to check your coding style. It has a huge number of available rules and it is a top pick if you don't need anything other than coding style checks.