difference between ts-loader?

[PatrickJS]

What's the difference between the two loaders?

[s-panferov]

This loader was created mostly to speed-up compilation in my own projects. Some of them are quite big and I wanted to have full control on how my files are compiled. There are three major points:

1. awesome-typescript-loader (atl) uses dependency resolution to build modules dependency graph. This speeds up build process in some corner cases, but adds a lot of additional complexity. Also it can re-emit all related files which is also useful in some corner cases.

2. atl has first-class integration with Babel and enables caching possibilities (for speed!)

3. atl is able to fork type-checker to a separate process, which also speeds-up some development scenarios (e.g. react with react-hot-loader)

[kevin-abiera]

That should be in the README 😃

[TheLarkInn]

Would you be willing to expand more on 'first-class integration with Babel'

[s-panferov]

@TheLarkInn when useBabel and useCache flags enabled, typescript's emit will be transplied with Babel and cached. So next time if source file (+environment) has the same checksum we can totally skip typescript's and babel's transpiling. This significantly reduces build time.

[admmasters]

I'm wondering whether this should be closed as imho its not really an issue. :-p

[s-panferov]

Moved to README. Thanks for all!

[caleb15]

People referencing this issue should also take a look at #497

According to @bengrunfeld ts-loader is about 10-17 seconds faster than awesome-typescript-loader.