Webpack Config Generator

Default output

With the defaults (production mode, TypeScript, Babel, a CSS loader and HtmlWebpackPlugin), the generator writes:

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

module.exports = {
  mode: 'production',
  entry: './src/index.js',
  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: 'bundle.[contenthash].js',
    clean: true,
  },
  resolve: { extensions: ['.ts','.tsx','.js'] },
  module: {
    rules: [
      { test: /\.tsx?$/, use: 'ts-loader', exclude: /node_modules/ },
      { test: /\.jsx?$/, exclude: /node_modules/, use: 'babel-loader' },
      { test: /\.css$/, use: ['style-loader', 'css-loader'] },
    ],
  },
  plugins: [
    new HtmlWebpackPlugin({ template: './src/index.html' }),
  ],
};

What each option writes

Fixed choices in the output

To keep the starter config clean, a few values are set for you rather than exposed as fields:

• Hashed filenames. output.filename is always bundle.[contenthash].js, which busts the browser cache whenever the bundle changes.
• Clean output. output.clean: true empties the output folder on each build, the webpack 5 replacement for clean-webpack-plugin.
• CSS is bundled, not extracted. style-loader injects styles through JavaScript. To emit a separate .css file for production, add MiniCssExtractPlugin yourself.
• Dev server basics. When enabled, devServer sets static, port: 3000 and hot: true. Add options such as historyApiFallback or proxy by hand if your app needs them.

Extending it further

The generated file is a starting point, not a full production setup. Common next steps you add by hand: MiniCssExtractPlugin for extracted CSS, sass-loader for .scss, webpack 5 asset modules for images and fonts, a devtool value for source maps, and a splitChunks block for code splitting.