fork-ts-checker-webpack-plugin VS babel-loader

Okay. The normal setup is that you use https://github.com/TypeStrong/ts-loader or https://github.com/TypeStrong/fork-ts-checker-webpack-plugin as part of your Webpack config. Those will run the TS compilation step as part of the Webpack processing sequence.

I work on a TypeScript project of similar size and complexity, and ours does not take even nearly that long to compile on save. Have you tried fork-ts-checker-webpack-plugin? We had compile times similar to yours until we started using it. Went from >60s to <1s builds in development. It's very simple to set up.

Yeah, I mean less loaders = less time. Did you try fork ts checker and compileOnly? https://github.com/TypeStrong/fork-ts-checker-webpack-plugin

That worker/memory limit is for the type checking only (rather than runtime memory), I believe this is done using https://github.com/TypeStrong/fork-ts-checker-webpack-plugin

There are many ways to integrate TypeScript with an existing Webpack configuration. If you use the babel-loader package to transpile JavaScript files, you can add the @babel/preset-typescript preset to generate JavaScript files and the Fork TS Checker Webpack Plugin package to run the TypeScript type checker so that the build fails if there are type errors.

esbuild-loader (secret sauce!) fork-ts-checker-webpack-plugin (helps us with typechecking) nodemon-webpack-plugin (We can also use webpack-dev-server)

I cloned github repo into a new dir, ran install with --frozen-lockfile and test-gui with --clean and got the same error. Looks like it's coming from fork-ts-checker-webpack-plugin and then found this among its reported issues: (https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/issues/562).

You may want to check out this webpack plugin [1], though I'm not sure how much it could get you there.

[1] https://github.com/TypeStrong/fork-ts-checker-webpack-plugin...

babel-loader

Uncaught TypeError: Object.assign is not a function I'm already using babel-loader to transpile ES6 to ES5, so all my other ES6 code is working. Yet, Object.assign() only works after I also import "babel-core/polyfill" in my codebase. I see that I can also fix this by importing babel-runtime, but I'd like to understand why Object.assign() requires more than what babel-loader performs — shouldn't babel-loader preprocess everything, including Object.assign()?

It looks like this may be an old version of webpack according to [this GitHub issue](https://github.com/babel/babel-loader/issues/798).

And babel/webpack seems to get upset at re-exporting things that don't exist at runtime (types and interfaces): https://github.com/babel/babel-loader/issues/603. So, you need to be careful to re-export your types with a different syntax, which is hard to remember when you're writing a file full of export * from 'foo'.

Apparently, this is usually a problem with Babel 7 and plugins but I've upgraded the plugins and still have this issue: https://github.com/babel/babel-loader/issues/560

There are many ways to integrate TypeScript with an existing Webpack configuration. If you use the babel-loader package to transpile JavaScript files, you can add the @babel/preset-typescript preset to generate JavaScript files and the Fork TS Checker Webpack Plugin package to run the TypeScript type checker so that the build fails if there are type errors.