-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Can compiler only emit declaration file ? #1866
Comments
There is no supported flags that would do that, only emit all or do not emit at all (--noEmit). Consider using --outDir and picking only the .d.ts files. |
I'm thinking of adding a --noEmitJs flag. Would you be willing to entertain that thought? |
if there is a compelling scenario. |
Scenario: Auto-Generate typings for a pure js project Currently typings for js projects are manually hand maintained. A ton of typings are out of date with the actual code. Typings are kind of documentation and if they are separate from code, they will eventually get out of sync. with --checkJs, JS lib authors get extra benefit of validating code with jsdoc typings. Being able to auto generate just .d.ts from their existing code would make life easier. This can be done as part of the build step. Basically if Proposal:
This would just generate a single .d.ts file from the project that you can add as part of package.json. No hand maintenance. |
Useful if you only want to generate the declaration files but not compile the js. Current usage for me would be that I'm generating an Electron application. I want the d.ts files in respective directories but the js files don't need to be created because they're made during application compilation and would cause only unnecessary clutter beforehand. |
Is there a way to only emit the declaration file (.d.ts) with the compiler and not the js file ?
The text was updated successfully, but these errors were encountered: