SWC Setup for JavaScript/TypeScript Transpilation

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

SWC Configuration for JavaScript/TypeScript Transpilation

SWC (Speedy Web Compiler) is a Rust-written transpiler compatible with Babel in transformations. It's 20–70 times faster than Babel on cold build. Next.js uses SWC by default since version 12. Vite uses it for TypeScript via esbuild, for JSX transformations via plugin. Jest with @swc/jest runs tests noticeably faster than with babel-jest.

Standalone installation

npm install --save-dev @swc/core @swc/cli

.swcrc — main config:

{
  "$schema": "https://swc.rs/schema.json",
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": true,
      "decorators": true,
      "dynamicImport": true
    },
    "transform": {
      "react": {
        "runtime": "automatic",
        "development": false,
        "refresh": false
      },
      "legacyDecorator": false,
      "decoratorMetadata": false
    },
    "target": "es2020",
    "loose": false,
    "externalHelpers": true,
    "keepClassNames": true
  },
  "env": {
    "targets": "> 0.5%, last 2 versions, not dead",
    "mode": "usage",
    "coreJs": "3"
  },
  "minify": false
}
npm install @swc/helpers  # externalHelpers: true — shared helpers instead of inline
npm install core-js@3     # for polyfills via env.mode: "usage"

Webpack integration via swc-loader

npm install --save-dev swc-loader
// webpack.config.js
module.exports = {
  module: {
    rules: [
      {
        test: /\.(ts|tsx|js|jsx)$/,
        exclude: /node_modules/,
        use: {
          loader: 'swc-loader',
          // options can be set inline or left empty — reads .swcrc
        },
      },
    ],
  },
};

Replacing babel-loader with swc-loader in real projects gives 3–5x build acceleration.

Jest with @swc/jest

npm install --save-dev @swc/jest
// jest.config.mjs
export default {
  transform: {
    '^.+\\.(ts|tsx|js|jsx)$': [
      '@swc/jest',
      {
        jsc: {
          parser: {
            syntax: 'typescript',
            tsx: true,
            decorators: true,
          },
          transform: {
            react: { runtime: 'automatic' },
          },
        },
        env: {
          targets: 'node16',
          mode: 'usage',
          coreJs: '3',
        },
      },
    ],
  },
  testEnvironment: 'node',
};

Timeline

Replacing Babel with SWC in existing project: 2–4 hours including testing. Setting up SWC for new project: 30–60 minutes.