It seems that tslint-auto-disable npm package doesn't contain built js files.

Steps to reproduce

1. npx tslint-auto-disable -p tsconfig.json -c tslint.json

Expected
The tslint:disable-next-line comments are added.

Actual

npx: installed 42 in 17.046s
Cannot find module '../dist/src/index'

Environment

• WSL (windows subsystem for linux), Ubuntu, Linux ********* 4.4.0-17763-Microsoft #55-Microsoft Sat Oct 06 18:05:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
• node -v: v8.9.4
• npm -v: 5.6.0
• "typescript": "^3.1.6"
• "tslint": "^5.11.0"

Doesn't work with tslint 6.1.2.

Everything is fine when tested with 5.20.1

Currently, when tslint-auto-disable is re-run it would insert another comment below a disabling comment. As long as #1 is not fixed, this is not of concern, as the disable comment disables all rules, but once we output more specific rule failures, this should be taken into account and existing comments should be updated.

Currently, tslint-auto-disable inserts the comment // tslint:disable-next-line. This turns of all rule validations for the next line. Ideally tslint-auto-disable would output a more specific disabeling comment, to only disable the rule which is actually failing.

Env: Windows & Ubuntu
Project: using Rush and pnpm
Powershell Command: npx tslint-auto-disable 'src/**/*.{ts,tsx}' -p .\tsconfig.json -c .\tslint.json -e ['*.d.ts']

getPreEmitDiagnostics emits a lot of failure on my node_module and lib *.d.ts files, which will block further actions.
I tried removing code snippet below and it worked.

        const diagnostics = ts.getPreEmitDiagnostics(program);
        if (diagnostics.length !== 0) {
            const message = diagnostics
                .map(d => showDiagnostic(d, program))
                .join("\n");
            throw new Error(message);
        }

So why do we need the getPreEmitDiagnostics in the first place?
Any idea why Diagnostics failed while I can run a successful build?

Thanks.