teaching VS ESLint

To minize the effort gts is a nice tool to help you setting up the project. Our of deployment/devliver purposes we also want to bundle the code to create nice and small artifacts. For those purposes we use esbuild. The whole example can be found here

Link

Use Static Code Analysis Tools: Tools like ESLint can help identify potential code injection points.

To learn more about ESLint, check out the official ESLint documentation. To learn more about Prettier, check out the official Prettier documentation.

Use linting tools to enforce consistent code style and catch potential issues. Prettier can help auto-format to a consistent style, while Eslint can help with more nuanced consistency checks that you can easily customize with your own plugins.

ESLint for code linting

ESLint

In this example, ESLint reported two errors due to violation of the rules no-unused-vars and no-undef: The ESLint GitHub project is organized in a monorepo, and you can consult more configuration options by looking into the @eslint/js package. The above config adds all recommended rules, which all have a severity level of error. We will learn more about violation severity in a minute.

✅ Angular 18 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with Cypress ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Provide component examples with Storybook ✅ Analyse your project with source-map-explorer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting ✅ AuditJS Audit this application using Sonatype OSS Index ✅ Auto-generate a CHANGELOG with auto-changelog

There is a popular open-source JavaScript linting tool called ESLint, which is used for automatically detecting incorrect patterns found in JavaScript code.

ESLint can help us identify many issues with just running a lint command in the project. We can use the rules available in ESLint or even find some helpful plugins eslint-plugin-unused-imports.