Any tips to increase performance?

[matthewjosephtaylor]

I notice this tool (which is awesome!) runs a bit slower than I would have anticipated.

I'm running it on a large monorepo with many workspace sub-projects, so I'm not to astonished it takes a while...but still. Like a minute or two.

If there is a known 'hotspot' in the code I'd love to take a crack at cooling it down.

Otherwise if there are any command line tweaks I'd be interested in those as well.

Thanks for such a useful tool (just what I needed, and I can see by the codebase that it must have taken quite some effort to code up)!

[timocov]

Hi there,

the tool relies on the typescript compiler a lot, and from my experience the most of the execution time is taken by compiling the code rather than the tool's internals.

What time it takes to compile your project? What do you use as an input for the tool - dts file(s) or ts? Do you compile your code in the pipeline/build steps somewhere before running the tool?

[matthewjosephtaylor]

Ah, that explains it!

I'm currently building each workspace 'sub-project' independently (ts->js via tsc -b) as needed.

So each sub-project has a /dist folder with 'compiled' js and .d.ts files inside of it.

Then rolling them all up via esbuild (sub-project dist/js -> singlle-file-js).

So it makes sense. Each sub-project isn't huge but there are like a dozen or so of them and so are adding up when done all at once.

So perhaps if I broke out the .d.ts files independent of the code and ran dts-bundler-generator on those directly (instead of the .d.ts + js) that might be faster.

I'll give that a shot and report back on findings....

[timocov]

Not sure if it would help, if you share the code I'd probably look closer and maybe can provide some suggestions. The reason why I asked about dts files is that the tool compiles ts files into dts first and then compiles dts files once again, but if at the first step the program contains only dts files (i.e. your input is dts file and any file that is used is dts) then the tool will skip that second compilation which might improve the performance a bit (you can try to play with --verbose flag to see more messages, but frankly I haven't used them for a while so not sure if they can help).