Skip to content

tsc --build ignores noEmitOnError=false #29851

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
GordonSmith opened this issue Feb 11, 2019 · 4 comments
Closed

tsc --build ignores noEmitOnError=false #29851

GordonSmith opened this issue Feb 11, 2019 · 4 comments
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug

Comments

@GordonSmith
Copy link

GordonSmith commented Feb 11, 2019

TypeScript Version: 3.3.1

Search Terms:
--build
noEmitOnError
generates
emit
error

Code

// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

tsc --build 

Expected behavior:
The output JS file should be emitted with the syntax error included.
Note: When calling tsc it works as expected.

Actual behavior:
No files are emitted

Playground Link:

Related Issues:

@sheetalkamat
Copy link
Member

@sheetalkamat sheetalkamat added the Working as Intended The behavior described is the intended behavior; this is not a bug label Feb 11, 2019
@GordonSmith
Copy link
Author

@sheetalkamat apologies, I should have read that document more thoroughly!

However I am still seeing this issue when there are only "warnings" which is not covered by the caveat - should I open a new issue?

@typescript-bot
Copy link
Collaborator

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

@octref
Copy link

octref commented Mar 19, 2019

But no emit on unused local is straight counter-productive. While writing programs unused locals will exist all times. Am I obliged to comment them out to just get TS to emit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Working as Intended The behavior described is the intended behavior; this is not a bug
Projects
None yet
Development

No branches or pull requests

4 participants