svelte-playground VS lint-staged

I also have a basic Svelte Starter --> https://github.com/kr40/svelte-playground.git

To lint staged files we’re going to use the lint-staged package: it’s easy to configure and supports different configurations per each project.

I added it to my pre-commit hook using lint-staged in package.json:

My second approach is to always ask ChatGPT to do a Bing (I wish it was google too, believe me) search for me and find tools that fit my criteria. And it did! I was recommended two packages, Husky and lint-staged, which work together! Husky is a package that provides ultra-fast modern native Git hooks, and lint-staged is a tool that allows running linters against staged Git files!

Since versioning via the nx-semantic-release plugin takes place by analyzing changes to related Typescript imports, we need to minimize these changes, to do this, we connect to the project https://www.npmjs.com/package/lint-staged and we add strictness to the Typescript code.

We are using husky to lint fix our code before committing it, and to make this process faster we are using a second package: lint-staged to only lint the staged code (newly added or modified code)

lint-staged: It enables us to run linters against staged git files. eslint and prettier will be executed by it.

Lint Staged: https://github.com/lint-staged/lint-staged

lint-staged is the second important tools we need here, install it via NPM.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.