Exit code always 1 with type check errors and --force active

[lepus2589]

Bug Report

• TSLint version: 4.3.1
• TypeScript version: 2.1.5
• Running TSLint via: CLI

TypeScript code being linted

(x: Number): void => {
    // x is not used in here
}

with tslint.json configuration: irrelevant

Actual behavior

Type checking is activated via the --type-check option as well as the --force switch. noUnusedParameters is active in the tsconfig.json, which is given to TSLint with the --project argument. The Typescript compiler will of course flag the parameter of the above function as unused.
The file runner.js prints the error message ('x' is declared but never used.) using an Error. It is not caught anywhere, so the exit code is 1 despite --force being used and the (valid) error message is followed by a stack trace.
Is this the intended behaviour?

Expected behavior

I would expect TSLint to print the error messages emitted by the Typescript compiler as linting errors, without an ugly stack trace containing TSLint source files. If not that, then at least when using the --force flag, the exit code should be 0, as stated in the documentation.

[psulek]

@lepus2589 Experiencing same problem with tslint version 4.4.2 and typescript 2.2.1.

[calidion]

any progress on this?
tslint with errors but still returns 1

[adidahiya]

@calidion the issue is marked as closed & fixed. if you're still seeing it you should probably open a new bug report. note that the --type-check option is deprecated.