ts-loader

> Typescript rewrote its compiler in Go, but that doesn't affect which runtime you use for the resulting Javascript code. It unfortunately has other implications, ts-loader (used by webpack) for example is not compatible with the new Go crap so you need to do weird pinning down to v6 to get your builds working again [1]. [1] https://github.com/TypeStrong/ts-loader/issues/1671

Theres tooling for this for webpack described: https://github.com/TypeStrong/ts-loader#faster-builds More generally though you have two loops one that does transpileOnly and one that doesn't. The latter is your type check process.

create-react-app is built on Webpack, for hot module replacement (HMR), and that requires a webpack loader. There's babel-loader and ts-loader. The stats in the projects are similar, but babel-loader is part of the babel project while ts-loader comes from an independent project, so it may be better integrated. Also ts-loader suggests using it with babel-loader. I'm not sure why, but if you install ts-loader and babel-loader you'll wind up with more dependencies than if you just install babel-loader. https://github.com/babel/babel-loader https://github.com/TypeStrong/ts-loader

ts-loader / fork-ts-checker-webpack-plugin maintainer here. I'm sorry to hear that's been your experience. It hasn't been my own; it could be worth you comparing your setup with one of the examples available. These are some good candidates: https://github.com/TypeStrong/ts-loader/tree/master/examples... https://github.com/TypeStrong/ts-loader/tree/master/examples... https://github.com/TypeStrong/ts-loader/tree/master/examples... (written by Kenneth Chau of the Outlook.com team) You may of course you may be using another typescript loader (there are several!). I thought it worth sharing in case you are using ts-loader and your config is catching you out. Best of luck!

I'm not sure if I understand fully this babel <-> typescript integration. Can you help me understand this? What's the point? So in future babel would be able to parse TS file and output JS file with all the transformations it supports? So it's useful if you want to use some new EsNext feature currently not supported by TS compiler? Is this the main advantage? Because for me it looks like a pretty weak reason (TS has improved a lot when it comes to supporting new ESNext features). Anyway, from what I understand TS provide API that for example webpack loaders use (like https://github.com/TypeStrong/ts-loader and https://github.com/s-panferov/awesome-typescript-loader) and it looks that those can be integrated with babel. Or is it mainly to support tools that depends on babel for parsing AST? And microsoft is willing to maintain this babel i

One of the maintainers of ts-loader here. Debugging original source is totally possible. Take a look at the setup here: https://github.com/TypeStrong/ts-loader/tree/master/examples... And in the official samples (WebPack 1): https://github.com/Microsoft/TypeScriptSamples/tree/master/r...

Hey rhymohr, I think I see what you mean. If you're already using something like Babel & Webpack, it should just be a matter of using a TypeScript loader like ts-loader[1] or awesome-typescript-loader[2]. TypeScript should just fit into that build step. Let me know how that ends up working out! [1]: https://github.com/TypeStrong/ts-loader [2]: https://github.com/s-panferov/awesome-typescript-loader