Separate Compilation on WebPack + TypeScript?

Question

typescript

Good afternoon.
Does anyone have experience implementing separate module compilation in Webpack/Typescript applications?
The fact is that at the request of the customer, it was decided to combine 3 fairly large web applications with a single entry point. (Previously, these were 3 different applications on different domains)
The problem is that app1 already contains N-number of chunks of several megabytes, and it’s going to be, let’s say, not quickly, but after integrating app2 and app3 into it, I’m generally afraid to imagine that will.
For example, in the same C / C ++ separate compilation is done very simply: roughly speaking, the source code is compiled into obj files and then all of them are linked into 1 binary.
I would like the same with webpack / typescript so that changes in app2 do not affect the rebuilding of app1 and app3.
Well, plus, if I'm a developer with a team on app3, then it's enough for me to compile app1 and app2 just once and continue working on app3 without rebuilding other applications.
Thank you.

Answer 1

Try awesome-ts-loader instead of the default ts-loader, it only rebuilds changed files.