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
I'm using webpack 3, ts-loader, and transpileOnly: true along with this fork-ts-checker-webpack-plugin.
My ts-config.json has "declaration": true, but I don't think I'm getting the type definitions because of transpileOnly: true which makes sense to me, since I didn't allow ts-loader to perform the computation of the types.
If that's the true cause, is there a way to output the definitions computed during this ts-checker phase? And is there a way to further bundle those definitions as webpack already does for the output .js file?
Thanks!
The text was updated successfully, but these errors were encountered:
Personally I've never used webpack in combination with "declaration": true and so I may not be fully understanding your setup. but Would it work if you had a separate process that generated the type definitions. So, another npm script that you used to just run tsc against to generate *.d.ts files? Just a thought... (not necessarily a useful one)
on Program class.
The fourth argument called emitOnlyDtsFiles might be something you are interested in. I don't have a time to implement this in near future so PR's are welcome :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm using webpack 3, ts-loader, and
transpileOnly: true
along with this fork-ts-checker-webpack-plugin.My
ts-config.json
has"declaration": true
, but I don't think I'm getting the type definitions because oftranspileOnly: true
which makes sense to me, since I didn't allow ts-loader to perform the computation of the types.If that's the true cause, is there a way to output the definitions computed during this ts-checker phase? And is there a way to further bundle those definitions as webpack already does for the output .js file?
Thanks!
The text was updated successfully, but these errors were encountered: