ESLint VS jsinspect

Website: eslint.org

Unfortunately, this did mean that configuration began to sprawl. At this point, I had configurations not just for Vite (shared with Vitest) and tsc, but also for Prettier, ESLint and even ShellCheck. Many of these files had shared settings that needed to match each other. This was somewhat manageable, until Vite was also in the mix.

1. ESLint Website: https://eslint.org/ Eslint is a static code analysis tool that checks your JavaScript/TypeScript code for errors and applies coding standards. Think of it as a spell-checker for your code.

I get it. If you're just here to find a good, working ESLint configuration for a NextJS project, then look no further. Copy what's below. Although, it's probably out of date, so you can find a version that's been updated since I published this post in my open source project Historio ➡️ in Github here ⬅️.

Does the library run in production, or is it limited to development or testing environments? Vulnerabilities in libraries like mocha or eslint can typically wait, while issues in runtime-critical libraries like express need immediate action.

Use tools like ESLint with security plugins:

Today was a great day, because I got to work on integrating ESLint into our codebase! I'm a funny code monkey. I enjoy good coding practices like linting, user/technical/product documentation, testing, accessibility, and security. These are topics that are usually deprioritized over shipping working code, because code can work without any of the things I listed as my programming passions. But if all those practices are implemented the code will rarely break (or be broken) and is more reliable code. Why not create "reliable working code" from the start?

The commonly used ones in this section are ESLint and Prettier, but there are also some confusion in their usage

There are two tools for that: Prettier and ESLint.

ESLint: Also static analysis