Skip to content
`tsc` with `--suppress` flag
TypeScript JavaScript
Branch: master
Clone or download
Latest commit 3ac8c63 Dec 5, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode Respect projectReferences Nov 22, 2019
bin Set up the package Nov 15, 2018
src Pass projectReferences to ts.createProgram Nov 22, 2019
.editorconfig Add .editorconfig Nov 15, 2018
.gitignore Set up the package Nov 15, 2018
LICENSE Initial commit Nov 5, 2018
package.json Respect projectReferences Nov 22, 2019
tsconfig.json Add build script Nov 15, 2018
yarn.lock Relax yargs version to '12 || 13' and add it to peerDependencies, #1 Mar 18, 2019


The purpose of the wrapper is to execute TypeScript compiler but suppress some error messages coming from certain files/folders. For example, this can be used to enable noImplicitAny in some parts of the project while keeping it disabled in others.


npm install -g tsc-silent


tsc-silent --project <path> [--suppress config | --suppressConfig path] [--compiler path] [--watch]


--project, -p    Path to tsconfig.json

--compiler       Path to typescript.js.
                 By default, uses `./node_modules/typescript/lib/typescript.js`.

--suppress       Suppressed erros.
                 E.g. `--suppress 7017@src/js/ 2322,2339,2344@/src/legacy/`.

--suppressConfig Path to supressed errors config.
                 See documentation for examples.

--watch, -w      Run in watch mode.

--stats          Print number of suppressed errors per path and error code.

Suppress config

You have to pass either --suppress or --suppressConfig.


Let's ignore error 7017 in src/js/ directory and errors 2322, 2339, 2344 in /src/legacy/:

tsc-silent -p tsconfig.json --suppress 7017@/src/js/ 2322,2339,2344@/src/legacy/

or, ignore all errors in /src/legacy/ folder

tsc-silent -p tsconfig.json --suppress @/src/legacy/

or, completely ignore all errors

tsc-silent -p tsconfig.json --suppress @


tsc-silent -p tsconfig.json --suppressConfig tsc-silent.config.js

See example.config.js.

Intended/typical use

Check out the article to see the intended use.

You can’t perform that action at this time.