Should tsBuildInfoFile and incremental options are removed in fixConfig function?

[timocov]

It looks like ts-node removes some compiler options that doesn't work with ts-node in

ts-node/src/index.ts

Lines 424 to 444 in 8706c31

	function fixConfig (ts: TSCommon, config: _ts.ParsedCommandLine) {
	// Delete options that *should not* be passed through.
	delete config.options.out
	delete config.options.outFile
	delete config.options.composite
	delete config.options.declarationDir
	delete config.options.declarationMap
	delete config.options.emitDeclarationOnly
	// Target ES5 output by default (instead of ES3).
	if (config.options.target === undefined) {
	config.options.target = ts.ScriptTarget.ES5
	}
	// Target CommonJS modules by default (instead of magically switching to ES6 when the target is ES6).
	if (config.options.module === undefined) {
	config.options.module = ts.ModuleKind.CommonJS
	}
	return config
	}

, right?

Setting tsBuildInfoFile compiler option (in my case for composite project) fail build with Emit skipped error. Should this option (quite possible that incremental should be removed too?) be removed along with other options in that function?

Related issue: #656

[wclr]

Wonder if incremental compilation can be supported by ts-node?

[blakeembrey]

@whitecolor I think that'd be really awesome, but I don't think the APIs are currently exposed.

@timocov Absolutely, feel free to make a PR.

[timocov]

@blakeembrey 👌. I just created #815 with removing these properties.

[wclr]

@blakeembrey the issue that tracks it
microsoft/TypeScript#29978