tsc - ignore errors at command line

Question

I have this:

$ tsc -m amd --outFile dist/out.js lib/index.ts

lib/index.ts(87,48): error TS1005: ';' expected.

Is there a command line option I can use to ignore errors?

Gallop

tsc --help doesn't provide any options to do this...what the heck – Gallop

What do you mean ignore errors? That should still output the compiled JS. There is a switch --noEmitOnError which is set to false by default. If you were to set it to true it would not emit JS (+ .d.ts). – Vincentvincenta

Are you using TSLint? Check for tslint.json, as that looks to be where that error would be originating from. – Vincentvincenta

What is the context of the error you're trying to ignore? Is it a npm library or is it your own code? What version of TypeScript do you have (tsc -v)? This sounds like a fatal syntax error that is preventing the compiler from completing compilation; it can't just be ignored. – Gesture

@AlexanderMills I noticed you recently started a bounty. Can you answer Greg's question? – Foretell

any errors, ultimately i just want to make sure it compiles to full possibility. of course if the error is too severe it wont be able to compile. – Gallop

@AlexanderMills You can ignore semantic errors (aka type erorrs, the kind of restrictions typescript imposes on top of JS) but you can't ignore syntactic errors (ie the syntax on JS/TS is invalid). The error you cite there is a sintactic error and will not be ignorable. If you don't specify other compiler options, the compiler will still emit JS even on semantic errors so taht should work out of the box. – Audun

Why don't you fix the error? – Wilt

@TitianCernicova-Dragomir It doesn't have to be a syntactic error. If he is using a linter (as Pricey pointed out), it could enforce setting semicolons where it wouldn't be needed to compile to valid JavaScript. – Satterlee

Can you give us the code so we can see why you have an error in the first place? – Despiteful

Answer 1

You can use another command like: build: tsc -m amd --outFile dist/out.js lib/index.ts new-build: npm run build || exit 0;

|| exit 0; always return 0; that is success code;

Kirsti

Answer 2

You can use // @ts-nocheck at the top of your files to have typescript not check them. This will still compile the code. To the point of @Jono on another question, yes, you will still have to go through every file to do this, although it is much less work than adding // @ts-ignore to every line. Source

Nosography

Answer 3

With the // @ts-ignore comment, Typescript compiler will ignore the line below it.

For example, you got an compiling error here:

Then just add // @ts-ignore

Audriaaudrie

In the example of changing an old project to typescript, you need a command line option so you don't have to add thousands of those comments... – Urson

Answer 4

No. There is no option to disable error Reports in TypeScript.

I just recently tried that, to improve my build pipeline. I checked the the TypeScript sources. It shouldn't be too complicated to code a flag to basically ignore all errors. But I didn't want to go through the whole PR/Approval Process for something that does the opposite of what typescript does. I found a different solution.

I also have a huge, converted code-base. There are other tools that transform TypeScript to JavaScript (but they lack Error Checking - which is what you want):

1. sucrase https://github.com/alangpierce/sucrase
2. @babel/preset-typescript https://babeljs.io/docs/en/babel-preset-typescript

Both work great in combination with rollup.js and their according plugins.

Inane

Answer 5

Typescript will soon have the --noCheck command line option that does exactly this.

The version that has this option seems to at the time of writing not be released yet, but the PR is merged on 12 Jun 2024, so it should come out in the next release, or if you build from source.

When the new version is out, you should be able to do:

tsc --noResolve --noCheck [file.ts]

(No resolve disables imports, if you want imported files to be included omit this)

Quota