ts-loader VS babel-plugin-styled-components

It'll be a little different than your typical "what is webpack?" article in that I write this as the maintainer of ts-loader, a loader used for integrating TypeScript with webpack. I've worked in the webpack ecosystem for some years now, and I'll share some of my experiences with you.

why I use @babel/preset-typescript over ts-loader and awesome-typescript-loader to complie TypeScript? it's blazingly faster than the others and has more perks(read #4) ts-loader doesn't natively support HMR(Hot Module Replacement) awesome-typescript-loader's latest release is on Jun 22, 2018 TypeScript With Babel: A Beautiful Marriage - Matt Turnbull's Post

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've recently tried SWC for building my project instead of ts-loader and was blown away by its performance (I got 8x-10x speedup on a Windows machine).

{ "compilerOptions": { "target": "esnext", "module": "esnext", "strict": true, "jsx": "preserve", "importHelpers": true, "moduleResolution": "node", "experimentalDecorators": true, "skipLibCheck": true, "esModuleInterop": true, "allowSyntheticDefaultImports": true, "sourceMap": true, "baseUrl": "./", "outDir": "./dist", // https://github.com/TypeStrong/ts-loader/issues/1138 "importsNotUsedAsValues": "preserve", "types": [ "webpack-env" ], "paths": { "@/*": [ "src/*" ], "@shared/*": [ "../shared/*" ] }, "lib": [ "esnext", "dom", "dom.iterable", "scripthost" ] }, "include": [ "src/**/*.ts", "src/**/*.tsx", "src/**/*.vue", "tests/**/*.ts", "tests/**/*.tsx", "../shared/**/*" ], "exclude": [ "node_modules" ] }

See https://github.com/TypeStrong/ts-loader#happypackmode. Switching to esbuild-loader cut my build time in half.

Unfortunately, one thing keeps me from fully migrating to SWC: it replaces Babel, but it seems to have no alternative for babel-plugin-styled-components, which is crucial for my work (I use server-side rendering for styles and want to have readable names for debugging).