fkill VS ESLint

Generally, npm libraries installed globally aren't standard library you'd use in your programs but more like CLI tools or full blown programs. As an example, fkill is the first one that comes to my mind.

fkill - Fabulously kill processes. Cross-platform.

Don't forget that Ewan is the author of eslint[1], which started a wave, eventually resulted in 10x performance improvements in frontend tooling, and even recent TypeScript rewrite to go[2].

[1] https://github.com/eslint/eslint

ESLint Pluggable Linter

5. Linters & Static Type Checking

So, I had to test this new version in a personal project to learn how to use all these new things along with other technologies and tools I’ve used for a long time and also love, like VSCode, ESLint, Prettier, and a bunch of other. And I did, but there’s a catch which makes the whole “experimental” thing have more sense: you can only use this through ng test.

ESLint: A tool for identifying and reporting on patterns found in ECMAScript/JavaScript code

While ESLint is the go-to tool for code quality in JavaScript, it doesn’t provide any built-in rule for this.

This linting is designed to work with eslint, which is very commonly used in the JavaScript world.

I noticed this issue only after running a linter. Sometimes we’re not familiar with the tricky edge cases or conventions of a particular language. A convenient way to catch and fix such issues — including formatting, styling, and even some security problems — is to use linters. For example, you can use golangci-lint for Go, ESLint for JavaScript, and Pylint for Python. In fact, almost every widely used programming language has its own linter or code quality tool. Linters are especially helpful when generating code with AI — they help keep your code clean and safe, at least to some degree.

Static code analysis tools scan code for potential issues before execution, catching bugs like null pointer dereferences or race conditions early. Daniel Vasilevski, Director and Owner of Bright Force Electrical, shares, “Utilizing static code analysis tools gives us a clear look at what’s going wrong before anything ever runs.” During a scheduling system rebuild, SonarQube flagged a concurrency flaw, preventing booking errors. A 2024 Synopsys report found that static analysis reduces production defects by 22%. Tools like ESLint for JavaScript or Checkstyle for Java complement testing, ensuring cleaner codebases.