@federato/ts-strictify
Runs TypeScript in strict mode on your
changed files.
How it works
When you start working on a new feature or fixing a bug, you will modify the
code base in one way or another. ts-strictify
will take a look at these
changes - and only these changes (!) and will complain, if the files you have
touched are not strict compliant.
That is different than TypeScript works. You could check a single file against
the compiler, but the compiler would also look up the imports and the imports of
the imports. Not exactly what you want, when you are looking for incrementally
update path.
Install
With npm
:
npm install --save-dev ts-strictify
With yarn
:
yarn add --dev ts-strictify
With pnpm
:
pnpm add --dev ts-strictify
Usage
With npm
:
npx ts-strictify
With yarn
:
yarn ts-strictify
With pnpm
:
pnpm ts-strictify
You can find a list of all available options here
.
Pre-Commit Hook
You can run ts-strictify
as a pre-commit hook using
husky
. Add the following to your
package.json
file.
{
"husky": {
"hooks": {
"pre-commit": "ts-strictify"
}
}
}
Options
Options:
--help Show help [boolean]
--version Show version number [boolean]
--project [string] [default: "./tsconfig.json"]
--targetBranch [string] [default: "main"]
--commitedFiles [boolean] [default: true]
--stagedFiles [boolean] [default: true]
--modifiedFiles [boolean] [default: true]
--untrackedFiles [boolean] [default: true]
--createdFiles [boolean] [default: true]
Thanks
Thanks to Christian Schröter for his work on the original ts-strictify project
this fork was based on!