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
Error TS5053 about 'noEmit' when noEmit isn't configured #1716
Comments
This was introduced with a fix for another bug - #1639, I forgot about emitDeclarationOnly. Should be an easy fix |
In my project I don't specify To work 100%, it seems like this function would need to change the value of |
Ah shoot, that's annoying. I forgot about watch mode doing weird things... It looks like watch mode doesn't currently support emitting files at all, which is probably another bug. |
Turns out that watch mode is more broken than I thought... yeah, it technically allows watching... but it doesn't actually use the watch program when doing conversion, so it is unnecessarily slow.. |
@Gerrit0 can you elaborate on this?
I’ve been starting to evaluate whether/how to use the watch mode in conjunction with project references over in |
68d5cbd fixed that :) the call to |
Search terms
TS5053, emitDeclarationOnly, noEmit
Expected Behavior
I'm building docs for a JS project, which uses
tsc
to emit type declarations, but not to compile anything. I'm invokingtypedoc
with the same config file, and things worked without errors under typedoc0.20
.Actual Behavior
After updating typedoc to
0.22
, when I run it I get the following error aboutnoEmit
, even though my configuration doesn't include that option.Steps to reproduce the bug
This is on OSX, node
16.8.0
. My package versions are current as of today:And I'm running
npx typedoc
in a folder containing the followingtsconfig.json
:The JS code doesn't seem to be relevant - the error displays even if the entry point file contains nothing but comments.
Has something changed here from previous versions? I can avoid the error by removing the
"emitDeclarationOnly": true,
config option, but since I'm not usingtsc
as a compiler this would mean I'd need separate configs fortsc
andtypedoc
. Is that the solution here?Thanks!
The text was updated successfully, but these errors were encountered: