Closed gablabelle closed 2 years ago
I think the main cause for this is that I made a method that turns this on automatically and that may be messing with it. Ill have a look
I think the main cause for this is that I made a method that turns this on automatically and that may be messing with it. Ill have a look!
I might be wrong but I feel this could be a huge improvement for performances in our monorepo.
I might be wrong but I feel this could be a huge improvement for performances in our monorepo.
I agree, for a monorepo this may be very benefitial. I had a look and it seems to do it here https://github.com/Floffah/esbuild-plugin-d.ts/blob/master/src/plugin.ts#L50-L58 if it is able to find your package.json although this may be broken and may be worth removing or making it toggleable. I will make a new release with these fixes soon
Also it seems that you should be using both createIncrementalProgram and createIncrementalCompilerHost in order to avoid the tsbuildinfo file to be ignore as explained here
According to the release notes
You seem to be missing the createIncrementalCompilerHost usage at https://github.com/Floffah/esbuild-plugin-d.ts/blob/master/src/plugin.ts#L61
Also it seems that you should be using both createIncrementalProgram and createIncrementalCompilerHost in order to avoid the tsbuildinfo file to be ignore as explained here
According to the release notes
You seem to be missing the createIncrementalCompilerHost usage at https://github.com/Floffah/esbuild-plugin-d.ts/blob/master/src/plugin.ts#L61
I'll add these when I get time to implement the automatic tsbuildinfo system
When running
yarn tsc --build
I get an outputtsconfig.tsbuildinfo
file used the the Typescript incremental builds. Subsequent builds are much faster.This file doesn't get generated when using
esbuild-plugin-d.ts
Even if I specify the
tsBuildInfoFile
option, same thing.