You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// An empty file will suffice, but let’s add a console.log to make more interesting.console.log('hello')
// Now this is the interesting file// tsconfig.json{"compilerOptions": {"noEmit": true}}
🙁 Actual behavior
This command behaves as tsc --noEmit
$ tsc --build
The --build and --noEmit options are mutually exclusive. I imagine --build is supposed to be mutually exclusive with the noEmit compiler option instead.
$ tsc --build --noEmit false
error TS5094: Compiler option '--noEmit' may not be used with '--build'.
🙂 Expected behavior
My preferred solution is that --build disables the noEmit compiler option.
Another option is that --build fails if noEmit is true.
Additional information about the issue
I think the tsc --build option is great. I prefer this over running tsc without it.
I also like the idea of running tsc without emitting anything. This is achieved by adding noEmit to tsconfig.json.
It’s unfortunate these two currently don’t play well together. As a workaround I now typically don’t use --build.
The text was updated successfully, but these errors were encountered:
🔎 Search Terms
TS5094
TS5094 noEmit build
🕗 Version & Regression Information
⏯ Playground Link
N/A, it’s a CLI bug
💻 Code
🙁 Actual behavior
This command behaves as
tsc --noEmit
The
--build
and--noEmit
options are mutually exclusive. I imagine--build
is supposed to be mutually exclusive with thenoEmit
compiler option instead.🙂 Expected behavior
My preferred solution is that
--build
disables thenoEmit
compiler option.Another option is that
--build
fails ifnoEmit
is true.Additional information about the issue
I think the
tsc --build
option is great. I prefer this over runningtsc
without it.I also like the idea of running
tsc
without emitting anything. This is achieved by addingnoEmit
totsconfig.json
.It’s unfortunate these two currently don’t play well together. As a workaround I now typically don’t use
--build
.The text was updated successfully, but these errors were encountered: