如何为多页面HTML5网站配置Webpack？附现有配置求指导

Hey there! Let's get your multi-page static HTML5 site set up with Webpack properly—you're already off to a good start with your current config, so we'll tweak and expand it to hit all your requirements.

Key Concepts for Multi-Page Sites #

For static multi-page projects, the core changes involve:

• Defining multiple entry points (one per page)
• Using multiple instances of html-webpack-plugin to generate each page and inject its corresponding JS/CSS assets
• Ensuring each page's resources are bundled together without overlap

Step 1: Update Dependencies #

First, let's add the essential tools for handling HTML and compressing CSS in production:

npm install html-webpack-plugin optimize-css-assets-webpack-plugin --save-dev

Also, add a browserslist field to your package.json—this tells autoprefixer which browsers to target for CSS prefixing.

Step 2: Full Config Examples #

Here's how to adjust your files to support multi-page sites, while meeting all your requirements. We'll use two example pages (index and about)—you can extend this pattern for as many pages as you need.

Updated package.json

{
  "name": "me",
  "version": "1.0.0",
  "description": "",
  "main": "app.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "webpack --mode production"
  },
  "author": "Ayan Dey",
  "license": "MIT",
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 8"
  ],
  "devDependencies": {
    "babel-core": "^6.26.3",
    "babel-loader": "^7.1.4",
    "babel-preset-es2015": "^6.24.1",
    "css-loader": "^0.28.11",
    "extract-text-webpack-plugin": "^4.0.0-beta.0",
    "html-webpack-plugin": "^3.2.0",
    "optimize-css-assets-webpack-plugin": "^5.0.1",
    "postcss-loader": "^2.1.5",
    "style-loader": "^0.21.0",
    "url-loader": "^1.0.1",
    "webpack": "^4.8.3",
    "webpack-cli": "^2.1.3"
  }
}

Updated webpack.config.js

const ExtractTextPlugin = require("extract-text-webpack-plugin");
const HtmlWebpackPlugin = require("html-webpack-plugin");
const OptimizeCSSAssetsPlugin = require("optimize-css-assets-webpack-plugin");
const path = require("path");

// Create separate ExtractTextPlugin instances for each page's CSS
const extractIndexCSS = new ExtractTextPlugin("index.styles.min.css");
const extractAboutCSS = new ExtractTextPlugin("about.styles.min.css");

module.exports = {
  // Define entry points: key = chunk name, value = path to the page's main JS file
  entry: {
    index: "./src/pages/index/index.js",
    about: "./src/pages/about/about.js"
  },
  output: {
    path: path.resolve(__dirname, "dist"),
    // Use [name] to dynamically generate filenames based on entry chunk names
    filename: "[name].bundle.min.js"
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        loader: "babel-loader?presets[]=es2015",
        exclude: /node_modules/
      },
      {
        test: /\.css$/,
        use: extractIndexCSS.extract(["css-loader", "postcss-loader"]),
        // Apply this rule only to the index page's CSS files
        include: path.resolve(__dirname, "src/pages/index")
      },
      {
        test: /\.css$/,
        use: extractAboutCSS.extract(["css-loader", "postcss-loader"]),
        // Apply this rule only to the about page's CSS files
        include: path.resolve(__dirname, "src/pages/about")
      },
      {
        test: /\.(svg|gif|jpg|png|eot|woff|ttf)$/,
        loader: "url-loader",
        options: {
          // Inline small assets; output larger ones to dist/assets
          limit: 8192,
          name: "assets/[name].[hash:8].[ext]"
        }
      }
    ]
  },
  optimization: {
    // Ensure CSS is compressed in production mode
    minimizer: [new OptimizeCSSAssetsPlugin({})]
  },
  plugins: [
    extractIndexCSS,
    extractAboutCSS,
    // Generate index.html and inject only its corresponding JS/CSS
    new HtmlWebpackPlugin({
      template: "./src/pages/index/index.html",
      filename: "index.html",
      chunks: ["index"]
    }),
    // Generate about.html and inject only its corresponding JS/CSS
    new HtmlWebpackPlugin({
      template: "./src/pages/about/about.html",
      filename: "about.html",
      chunks: ["about"]
    })
  ]
};

postcss.config.js (unchanged, but fully functional with the setup)

module.exports = {
  plugins: [require("autoprefixer")]
};

Recommended Project Structure #

Organize your files like this to keep things clean and scalable:

your-project/
├── src/
│   ├── pages/
│   │   ├── index/
│   │   │   ├── index.html
│   │   │   ├── index.js
│   │   │   └── styles.css
│   │   └── about/
│   │       ├── about.html
│   │       ├── about.js
│   │       └── styles.css
│   └── assets/ (optional, for shared images/fonts)
├── dist/ (generated automatically by Webpack)
├── package.json
├── webpack.config.js
└── postcss.config.js

How This Meets Your Requirements #

1. Single-page JS bundling & compression: Each page has its own entry JS, bundled into a unique [name].bundle.min.js file. Webpack's production mode automatically compresses JS.
2. ES6 to ES5: Your existing babel-loader setup handles this—just make sure all page-specific JS is imported through the entry points.
3. Single-page CSS bundling & compression: Each page's CSS is extracted into a dedicated [name].styles.min.css file, and OptimizeCSSAssetsPlugin compresses it in production.
4. Auto-prefix CSS: autoprefixer in postcss-loader adds prefixes based on the browserslist rules in your package.json.
5. Bundle per-page resources: Entry points and html-webpack-plugin instances ensure each page's JS, CSS, and assets are bundled together and only injected into that page's HTML.

Alternatives to html-webpack-plugin #

While html-webpack-plugin is the most reliable and maintainable method for multi-page sites, you could manually copy HTML files to the dist folder and replace resource paths (using copy-webpack-plugin with transforms). However, this is error-prone and far less scalable—stick with html-webpack-plugin for best results.

内容的提问来源于stack exchange，提问作者Ayan