🎯

webpack

🎯Skill
g1joshi/agent-skills1 Installs9Last Updated Feb 10, 2026

Installation

$npx skills add g1joshi/agent-skills --skill webpack

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh Β· Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/webpack
Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder β†’
  • This project .claude/skills/webpack/
  • All projects ~/.claude/skills/webpack/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

Expert Webpack assistance covering asset bundling, code splitting, loaders, plugins, caching strategies, and webpack.config.js optimization. Use when configuring Webpack 5, optimizing bundle sizes, setting up Babel/TypeScript loaders, or configuring Module Federation.

Webpack

Webpack is the grandfather of bundlers. While slower than Vite, it offers unparalleled flexibility and remains the engine behind Next.js (legacy), Angular, and enterprise apps.

When to Use

  • Enterprise Webpack 5 Bundling: Managing complex enterprise web applications with custom asset transformations and polyfills.
  • Module Federation Micro-Frontends: Sharing modules, components, and runtime state dynamically across distributed micro-apps.
  • Granular Code Splitting & Caching: Fine-tuning split chunks, vendor optimization, and deterministic bundle hashing.
  • Custom Loader & Plugin Architectures: Extending compilation pipelines with custom AST manipulation and build hooks.

Quick Start

1. Minimal webpack.config.js

const path = require("path");
const HtmlWebpackPlugin = require("html-webpack-plugin");

module.exports = {
  entry: "./src/index.js",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: "[name].[contenthash].js",
    clean: true,
  },
  module: {
    rules: [
      { test: /\.css$/i, use: ["style-loader", "css-loader"] },
      { test: /\.(png|svg|jpg)$/i, type: "asset/resource" },
    ],
  },
  plugins: [new HtmlWebpackPlugin({ template: "./public/index.html" })],
  optimization: {
    splitChunks: { chunks: "all" },
  },
};

2. Build via CLI

npx webpack --mode production

Core Concepts

Production Webpack 5 Configuration (webpack.config.js)

Configuring modern performance, caching, and splitChunks optimization:

const path = require("node:path");
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
const CssMinimizerPlugin = require("css-minimizer-webpack-plugin");
const TerserPlugin = require("terser-webpack-plugin");

const isProd = process.env.NODE_ENV === "production";

module.exports = {
  mode: isProd ? "production" : "development",
  entry: "./src/index.tsx",
  output: {
    path: path.resolve(__dirname, "dist"),
    filename: isProd ? "js/[name].[contenthash:8].js" : "js/[name].js",
    chunkFilename: isProd
      ? "js/[name].[contenthash:8].chunk.js"
      : "js/[name].chunk.js",
    clean: true,
  },
  resolve: {
    extensions: [".tsx", ".ts", ".js"],
    alias: {
      "@": path.resolve(__dirname, "src"),
    },
  },
  module: {
    rules: [
      {
        test: /\.(ts|tsx)$/,
        exclude: /node_modules/,
        use: {
          loader: "swc-loader",
        },
      },
      {
        test: /\.css$/,
        use: [
          isProd ? MiniCssExtractPlugin.loader : "style-loader",
          "css-loader",
          "postcss-loader",
        ],
      },
      {
        test: /\.(png|svg|jpg|jpeg|gif)$/i,
        type: "asset",
        parser: {
          dataUrlCondition: { maxSize: 8 * 1024 }, // Inline under 8KB
        },
      },
    ],
  },
  optimization: {
    minimize: isProd,
    minimizer: [new TerserPlugin(), new CssMinimizerPlugin()],
    splitChunks: {
      chunks: "all",
      cacheGroups: {
        defaultVendors: {
          test: /[\\/]node_modules[\\/]/,
          name: "vendors",
          priority: -10,
          reuseExistingChunk: true,
        },
      },
    },
  },
  plugins: [
    ...(isProd
      ? [
          new MiniCssExtractPlugin({
            filename: "css/[name].[contenthash:8].css",
          }),
        ]
      : []),
  ],
  devServer: {
    port: 3000,
    hot: true,
    historyApiFallback: true,
  },
};

Module Federation Micro-Frontend Configuration

Exposing and consuming shared components at runtime:

const { ModuleFederationPlugin } = require("webpack").container;

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      name: "host_app",
      remotes: {
        checkout: "checkout@https://cdn.example.com/checkout/remoteEntry.js",
      },
      shared: {
        react: { singleton: true, requiredVersion: "^19.0.0" },
        "react-dom": { singleton: true, requiredVersion: "^19.0.0" },
      },
    }),
  ],
};

Filesystem Caching for Accelerated Builds

Enabling persistent caching to cut subsequent build times by over 80%:

module.exports = {
  cache: {
    type: "filesystem",
    buildDependencies: {
      config: [__filename],
    },
  },
};

Common Patterns

Code Splitting via Dynamic Imports

Problem: Reduce initial page weight by deferring heavy components until needed.
Solution: Use ECMAScript dynamic import().

// Dynamic route or modal loading
button.addEventListener("click", async () => {
  const { renderModal } = await import(
    /* webpackChunkName: "modal" */ "./components/Modal"
  );
  renderModal();
});

Long-Term Caching Optimization

Problem: Ensure updated bundles bust browser cache while unchanged vendor libraries remain cached.
Solution: Separate runtime chunk and extract vendor libraries.

module.exports = {
  optimization: {
    runtimeChunk: "single",
    splitChunks: {
      cacheGroups: {
        vendor: {
          test: /[\\/]node_modules[\\/]/,
          name: "vendors",
          chunks: "all",
        },
      },
    },
  },
};

Best Practices

Do:

  • Enable cache: { type: "filesystem" } in Webpack 5 to dramatically reduce CI/CD build times.
  • Use swc-loader or esbuild-loader in place of babel-loader for up to 10x faster transpilation.
  • Use [contenthash:8] in production output filenames for optimal long-term browser HTTP caching.
  • Externalize and isolate shared dependencies with singleton: true in Module Federation.

Don't:

  • Build large production SPAs without configuring splitChunks to separate vendor and application code.
  • Include expensive development plugins (e.g. detailed source map generators) in production configurations.
  • Commit dist/ or .cache/ build output directories to version control.

Troubleshooting

ErrorCauseSolution
Module not found: Error: Can't resolve '...'File extension missing from resolve.extensions arrayAdd resolve: { extensions: ['.ts', '.tsx', '.js', '.json'] } to webpack.config.js.
Out of memory (JavaScript heap out of memory)Heavy source maps or source analysis on large dependency graphSwitch devtool to eval-cheap-module-source-map for development; exclude node_modules from loaders.
Injected styles not showing in productionstyle-loader used instead of extracting CSS in productionUse MiniCssExtractPlugin.loader in production builds instead of style-loader.

References

More from this repository10