Webpack CLI: Command Line Interface for webpack
/webpack-cli
Webpack CLI is the official command-line interface for the webpack bundler, exposing webpack's own config-file options as flags you type at a terminal. It isn't really an independent choice — once you're on webpack, this is how you run it day to day. Reach for it when you want `build`, `serve`, and `watch` without hand-writing a Node script around webpack's API; skip webpack itself if a leaner bundler is what you actually want.
What Webpack CLI Does
Webpack CLI is the official command-line interface for webpack, installed as the `webpack-cli` npm package once webpack itself is in the project. It exposes webpack's config-file options as command-line flags — a flag at invocation overrides that option in the config file — and runs the `build`, `serve`, `watch`, `configtest`, `info`, and `version` commands developers reach for during everyday webpack work.
Core Commands and Capabilities
- ✓`build` (aliases `bundle`, `b`) runs webpack and is the default command — running `webpack-cli` with no subcommand bundles your project.
- ✓`serve` (aliases `server`, `s`) runs webpack behind a development server that reloads as files change.
- ✓`watch` (alias `w`) reruns webpack automatically whenever a watched file changes, without starting a dev server.
- ✓`configtest` (alias `t`) checks that a webpack configuration file is valid.
- ✓`info` (alias `i`) prints details about the local environment.
- ✓`version` (alias `v`) prints version numbers for webpack, webpack-cli, webpack-dev-server, and other installed commands.
- ✓`help` (alias `h`) prints usage help for a command or option.
- ✓Exit codes separate causes for scripts: `0` for success, `1` for errors thrown by webpack itself, `2` for a configuration/options problem or an internal error.
Streamlining Webpack Workflows
- •Bundling a production build by running `build` — or nothing at all, since it's the default command — instead of writing a custom Node script around webpack's API.
- •Running a local dev loop with `serve`, which starts a dev server and reloads on file changes.
- •Catching a broken webpack config with `configtest` before it reaches CI or a teammate's machine.
- •Scaffolding a new webpack project with `create-webpack-app init` instead of copying a `webpack.config.js` from a tutorial.
- •Pulling environment details with `info` when filing a bug report or debugging a version mismatch.
Installing Webpack CLI
If you've already worked through webpack's own Getting Started guide, webpack CLI is installed already — that guide pulls it in for you. Starting from scratch, add it as a dev dependency with `npm install --save-dev webpack-cli`, `yarn add webpack-cli --dev`, or `pnpm add --D webpack-cli`. Webpack itself needs to be in the project too, since webpack CLI is a companion to webpack rather than a bundler on its own.
Starting a New Webpack Project
To start a project from nothing, run `npx create-webpack-app init` and answer its prompts — it asks about options like SCSS, TypeScript, or PWA support before generating the project. If you set webpack up by following its own Getting Started guide, you can skip that scaffold; webpack CLI is already there and its commands are ready to use. From either starting point, `build` bundles the project, `serve` runs it behind a dev server, and `watch` rebuilds it as you edit files.
Strengths
- ✓It's the official CLI maintained under the webpack GitHub organization, so its commands map directly to what webpack's own API supports.
- ✓Seven purpose-built commands — `build`, `configtest`, `help`, `info`, `serve`, `version`, `watch` — cover bundle, validate, serve, and watch without custom npm scripts for each.
- ✓`create-webpack-app init` gives you a prompted scaffold instead of copying a `webpack.config.js` from somewhere else.
- ✓Exit codes distinguish webpack errors from configuration/options problems from success, which helps CI fail for the right reason.
- ✓MIT licensed, so there's no restriction on commercial use.
Considerations for Complex Configurations
- △The full command and flag reference lives in a separate document (packages/webpack-cli/README.md), not in the main README, so option-by-option behavior for complex configs isn't something these facts cover.
- △Webpack CLI isn't a standalone bundler — it requires webpack to already be part of the project, so it doesn't reduce webpack's own configuration surface, just gives you a CLI onto it.
- △No version number, release date, or changelog entry appears in the facts here, so there's no documented way to tell how current a given install is.
- △What `configtest` actually flags versus what it silently allows isn't spelled out in the README, so how far its validation reaches on a large, multi-target config is not clearly documented.
- △Beyond the npm/yarn/pnpm install commands and the `create-webpack-app` scaffold, the README doesn't cover migrating an existing complex `webpack.config.js`, multi-entry setups, or plugin authoring.
Other Build Tool CLIs
Frequently Asked Questions
Webpack CLI is released under the MIT license, per its GitHub repository listing.
Install Webpack CLI as a dev dependency with `npm install --save-dev webpack-cli`, `yarn add webpack-cli --dev`, or `pnpm add --D webpack-cli` — or skip the step entirely if you already followed webpack's own Getting Started guide, which installs it for you.
Webpack CLI can create new projects: running `npx create-webpack-app init` scaffolds one and prompts you for options such as SCSS, TypeScript, or PWA support.
Webpack CLI's main commands are `build` (default, aliased `bundle`/`b`), `serve` (aliased `server`/`s`), `watch` (aliased `w`), `configtest` (aliased `t`), `info` (aliased `i`), `version` (aliased `v`), and `help` (aliased `h`).
Webpack CLI reads the same options webpack's configuration file uses and exposes them as command-line flags; when a flag and the config file disagree on a given option, the flag passed on the command line takes priority.
The repository shows an active build pipeline (CI status and codecov badges), a GitHub Discussions board, and a Discord server — signs of ongoing maintenance, though no specific release cadence is stated in the facts here.
The problem it solves
webpack itself only exposes a JavaScript API — running a build from a terminal otherwise means writing a Node script that requires webpack, builds a compiler instance, and wires up watching or a dev server by hand. Webpack CLI turns that into commands: `build`, `serve`, `watch`, and the rest exist so a terminal invocation or an npm script can drive webpack instead of custom Node code doing it every time.
Who should try it — and who should skip
Try Webpack CLI if you're already on webpack and want its `build`/`serve`/`watch`/`configtest` commands instead of a hand-rolled Node script around the webpack API — `create-webpack-app` also helps the first time you set a project up. Don't evaluate it as a standalone decision if you haven't picked webpack yet: Webpack CLI doesn't bundle anything by itself, so the real question is whether webpack fits your project against something like Vite or esbuild, and Webpack CLI just comes along once that call is made.
Related repositories
Curious whether webpack-cli is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about webpack-cli.