webpack-dev-server vs nodemon vs http-server vs serve vs browser-sync vs live-server vs lite-server
Development Servers and Live Reload Tools Comparison
1 Year
webpack-dev-servernodemonhttp-serverservebrowser-synclive-serverlite-serverSimilar Packages:
What's Development Servers and Live Reload Tools?

These npm packages are development servers and live reload tools that facilitate web development by providing a local server environment, automatic reloading of the browser upon file changes, and various other features that enhance the development workflow. They help developers test their applications in real-time, ensuring a smoother and more efficient development process.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
webpack-dev-server13,843,6967,818541 kB383 months agoMIT
nodemon7,551,51926,471220 kB83 months agoMIT
http-server2,954,02913,791124 kB142-MIT
serve1,570,7679,54325.8 kB1415 months agoMIT
browser-sync791,91312,230628 kB5725 months agoApache-2.0
live-server87,7104,47053.7 kB216-MIT
lite-server29,6712,319-744 years agoMIT
Feature Comparison: webpack-dev-server vs nodemon vs http-server vs serve vs browser-sync vs live-server vs lite-server

Live Reload

  • webpack-dev-server:

    webpack-dev-server supports hot module replacement, allowing you to see updates in real-time without refreshing the entire page, enhancing the development experience.

  • nodemon:

    nodemon does not provide live reload for the browser; instead, it automatically restarts the Node.js server when file changes are detected, which is crucial for backend development.

  • http-server:

    http-server does not support live reloading; it simply serves static files without any additional features for automatic updates or synchronization.

  • serve:

    serve does not include live reload features; it serves static files without automatic updates or refresh capabilities.

  • browser-sync:

    Browser-Sync provides advanced live reloading capabilities, allowing you to see changes in real-time across multiple devices and browsers. It synchronizes interactions, so scrolling, clicking, and form inputs are mirrored on all connected devices.

  • live-server:

    live-server provides live reload capabilities, refreshing the browser automatically when changes are made to files, making it ideal for static sites.

  • lite-server:

    lite-server offers live reload functionality, automatically refreshing the browser when files change, making it easy to see updates immediately during development.

Configuration Complexity

  • webpack-dev-server:

    webpack-dev-server requires a Webpack configuration but provides powerful features like hot module replacement, which may add complexity compared to simpler servers.

  • nodemon:

    nodemon requires minimal configuration, mainly focusing on the scripts you want to monitor for changes, making it easy to integrate into existing Node.js applications.

  • http-server:

    http-server is extremely simple to set up with minimal configuration, making it ideal for quick tests or serving static files without hassle.

  • serve:

    serve is simple to use with minimal configuration, allowing you to get up and running quickly with static file serving.

  • browser-sync:

    Browser-Sync requires some configuration, especially for advanced features like synchronization across devices, but it is generally straightforward and well-documented.

  • live-server:

    live-server is very easy to use with no configuration needed, making it perfect for developers looking for a quick and simple solution.

  • lite-server:

    lite-server requires minimal configuration and is easy to set up, making it a good choice for small projects or quick prototypes.

Use Case

  • webpack-dev-server:

    Best for projects using Webpack, providing advanced features like hot module replacement for a more efficient development workflow.

  • nodemon:

    Essential for backend development in Node.js applications, allowing for automatic restarts of the server on file changes, streamlining the development process.

  • http-server:

    Best suited for serving static files quickly without any additional features, making it perfect for quick tests or serving static content.

  • serve:

    Ideal for serving single-page applications and static sites with minimal fuss, providing a straightforward command-line interface.

  • browser-sync:

    Ideal for front-end developers who need to test responsive designs across multiple devices and browsers simultaneously, making it great for collaborative work.

  • live-server:

    Perfect for static sites and quick prototyping, providing a simple way to see changes in real-time without configuration.

  • lite-server:

    Great for small projects or when you need a quick server with live reload capabilities, especially for static sites.

Performance

  • webpack-dev-server:

    webpack-dev-server is optimized for development, providing fast rebuilds and hot module replacement, but can consume more resources compared to simpler servers.

  • nodemon:

    nodemon's performance is tied to the Node.js application it monitors; it does not affect the performance of the application itself but can slow down restarts if many files are watched.

  • http-server:

    http-server is lightweight and fast, making it ideal for serving static files without any performance bottlenecks.

  • serve:

    serve is fast and efficient for serving static files, with minimal performance impact, making it suitable for production-like environments.

  • browser-sync:

    Browser-Sync can introduce some overhead due to its synchronization features, but it is generally performant for most development scenarios.

  • live-server:

    live-server is lightweight and performs well for static sites, but may slow down with many simultaneous connections due to its simplicity.

  • lite-server:

    lite-server is efficient for small projects, but performance may vary with larger applications due to its live reload capabilities.

Ecosystem Integration

  • webpack-dev-server:

    webpack-dev-server is designed to work with Webpack, providing a powerful development environment that leverages Webpack's capabilities for modern web applications.

  • nodemon:

    nodemon integrates seamlessly with Node.js applications, making it a crucial tool for backend development and enhancing the development workflow.

  • http-server:

    http-server is a standalone tool and does not integrate with other tools but is useful for quick tests and serving static files.

  • serve:

    serve is a standalone tool that does not require integration, making it easy to use for serving static files without additional setup.

  • browser-sync:

    Browser-Sync integrates well with various build tools and task runners, enhancing its capabilities for modern web development workflows.

  • live-server:

    live-server is a standalone tool that does not require integration with other tools, making it simple to use for static sites.

  • lite-server:

    lite-server can be easily integrated into existing projects and works well with other tools, making it a flexible choice for developers.

How to Choose: webpack-dev-server vs nodemon vs http-server vs serve vs browser-sync vs live-server vs lite-server
  • webpack-dev-server:

    Opt for webpack-dev-server if you're using Webpack for your build process and need a development server that supports hot module replacement, allowing for seamless updates without a full page reload.

  • nodemon:

    Choose nodemon if you're working with Node.js applications and want automatic restarts of your server whenever file changes are detected. It's essential for backend development to streamline the workflow.

  • http-server:

    Select http-server for a simple and lightweight solution to serve static files quickly without any additional features. It's perfect for quick tests or serving static content without overhead.

  • serve:

    Select serve for a simple command-line static file server that is easy to use and configure. It's great for serving single-page applications and static sites with minimal fuss.

  • browser-sync:

    Choose Browser-Sync if you need a powerful tool that not only serves your files but also synchronizes interactions across multiple devices and browsers, making it ideal for testing responsive designs.

  • live-server:

    Use live-server for an easy-to-use server that automatically reloads your browser when changes are detected. It's suitable for static sites and quick prototyping.

  • lite-server:

    Opt for lite-server if you want a simple development server with live reload capabilities and a minimal setup. It's great for small projects or when you need a quick server without complex configurations.

README for webpack-dev-server

npm node tests coverage discussion downloads contributors

webpack-dev-server

Use webpack with a development server that provides live reloading. This should be used for development only.

It uses webpack-dev-middleware under the hood, which provides fast in-memory access to the webpack assets.

Table of Contents

Getting Started

First things first, install the module:

npm install webpack-dev-server --save-dev

or

yarn add -D webpack-dev-server

or

pnpm add -D webpack-dev-server

Note: While you can install and run webpack-dev-server globally, we recommend installing it locally. webpack-dev-server will always use a local installation over a global one.

Usage

There are two main, recommended methods of using the module:

With the CLI

The easiest way to use it is with the webpack CLI. In the directory where your webpack.config.js is, run:

npx webpack serve

Following options are available with webpack serve:

Usage: webpack serve|server|s [entries...] [options]

Run the webpack dev server.

Options:
  -c, --config <value...>                             Provide path to a webpack configuration file e.g. ./webpack.config.js.
  --config-name <value...>                            Name of the configuration to use.
  -m, --merge                                         Merge two or more configurations using 'webpack-merge'.
  --disable-interpret                                 Disable interpret for loading the config file.
  --env <value...>                                    Environment passed to the configuration when it is a function.
  --node-env <value>                                  Sets process.env.NODE_ENV to the specified value.
  --define-process-env-node-env <value>               Sets process.env.NODE_ENV to the specified value. (Currently an alias for `--node-env`)
  --analyze                                           It invokes webpack-bundle-analyzer plugin to get bundle information.
  --progress [value]                                  Print compilation progress during build.
  -j, --json [value]                                  Prints result as JSON or store it in a file.
  --fail-on-warnings                                  Stop webpack-cli process with non-zero exit code on warnings from webpack
  -d, --devtool <value>                               A developer tool to enhance debugging (false | eval | [inline-|hidden-|eval-][nosources-][cheap-[module-]]source-map).
  --no-devtool                                        Negative 'devtool' option.
  --entry <value...>                                  A module that is loaded upon startup. Only the last one is exported.
  --mode <value>                                      Enable production optimizations or development hints.
  --name <value>                                      Name of the configuration. Used when loading multiple configurations.
  -o, --output-path <value>                           The output directory as **absolute path** (required).
  --stats [value]                                     Stats options object or preset name.
  --no-stats                                          Negative 'stats' option.
  -t, --target <value...>                             Environment to build for. Environment to build for. An array of environments to build for all of them when possible.
  --no-target                                         Negative 'target' option.
  --watch-options-stdin                               Stop watching when stdin stream has ended.
  --no-watch-options-stdin                            Negative 'watch-options-stdin' option.
  --allowed-hosts <value...>                          Allows to enumerate the hosts from which access to the dev server are allowed (useful when you are proxying dev server, by default is 'auto').
  --allowed-hosts-reset                               Clear all items provided in 'allowedHosts' configuration. Allows to enumerate the hosts from which access to the dev server are allowed (useful when you are proxying dev server, by default is 'auto').
  --bonjour                                           Allows to broadcasts dev server via ZeroConf networking on start.
  --no-bonjour                                        Disallows to broadcasts dev server via ZeroConf networking on start.
  --no-client                                         Disables client script.
  --client-logging <value>                            Allows to set log level in the browser.
  --client-overlay                                    Enables a full-screen overlay in the browser when there are compiler errors or warnings.
  --no-client-overlay                                 Disables the full-screen overlay in the browser when there are compiler errors or warnings.
  --client-overlay-errors                             Enables a full-screen overlay in the browser when there are compiler errors.
  --no-client-overlay-errors                          Disables the full-screen overlay in the browser when there are compiler errors.
  --client-overlay-warnings                           Enables a full-screen overlay in the browser when there are compiler warnings.
  --no-client-overlay-warnings                        Disables the full-screen overlay in the browser when there are compiler warnings.
  --client-overlay-runtime-errors                     Enables a full-screen overlay in the browser when there are uncaught runtime errors.
  --no-client-overlay-runtime-errors                  Disables the full-screen overlay in the browser when there are uncaught runtime errors.
  --client-overlay-trusted-types-policy-name <value>  The name of a Trusted Types policy for the overlay. Defaults to 'webpack-dev-server#overlay'.
  --client-progress                                   Prints compilation progress in percentage in the browser.
  --no-client-progress                                Does not print compilation progress in percentage in the browser.
  --client-reconnect [value]                          Tells dev-server the number of times it should try to reconnect the client.
  --no-client-reconnect                               Tells dev-server to not to try to reconnect the client.
  --client-web-socket-transport <value>               Allows to set custom web socket transport to communicate with dev server.
  --client-web-socket-url <value>                     Allows to specify URL to web socket server (useful when you're proxying dev server and client script does not always know where to connect to).
  --client-web-socket-url-hostname <value>            Tells clients connected to devServer to use the provided hostname.
  --client-web-socket-url-pathname <value>            Tells clients connected to devServer to use the provided path to connect.
  --client-web-socket-url-password <value>            Tells clients connected to devServer to use the provided password to authenticate.
  --client-web-socket-url-port <value>                Tells clients connected to devServer to use the provided port.
  --client-web-socket-url-protocol <value>            Tells clients connected to devServer to use the provided protocol.
  --client-web-socket-url-username <value>            Tells clients connected to devServer to use the provided username to authenticate.
  --compress                                          Enables gzip compression for everything served.
  --no-compress                                       Disables gzip compression for everything served.
  --history-api-fallback                              Allows to proxy requests through a specified index page (by default 'index.html'), useful for Single Page Applications that utilise the HTML5 History API.
  --no-history-api-fallback                           Disallows to proxy requests through a specified index page.
  --host <value>                                      Allows to specify a hostname to use.
  --hot [value]                                       Enables Hot Module Replacement.
  --no-hot                                            Disables Hot Module Replacement.
  --ipc [value]                                       Listen to a unix socket.
  --live-reload                                       Enables reload/refresh the page(s) when file changes are detected (enabled by default).
  --no-live-reload                                    Disables reload/refresh the page(s) when file changes are detected (enabled by default).
  --open [value...]                                   Allows to configure dev server to open the browser(s) and page(s) after server had been started (set it to true to open your default browser).
  --no-open                                           Does not open the default browser.
  --open-target <value...>                            Opens specified page in browser.
  --open-app-name <value...>                          Open specified browser.
  --open-reset                                        Clear all items provided in 'open' configuration. Allows to configure dev server to open the browser(s) and page(s) after server had been started (set it to true to open your default browser).
  --open-target-reset                                 Clear all items provided in 'open.target' configuration. Opens specified page in browser.
  --open-app-name-reset                               Clear all items provided in 'open.app.name' configuration. Open specified browser.
  --port <value>                                      Allows to specify a port to use.
  --server-type <value>                               Allows to set server and options (by default 'http').
  --server-options-passphrase <value>                 Passphrase for a pfx file.
  --server-options-request-cert                       Request for an SSL certificate.
  --no-server-options-request-cert                    Does not request for an SSL certificate.
  --server-options-ca <value...>                      Path to an SSL CA certificate or content of an SSL CA certificate.
  --server-options-ca-reset                           Clear all items provided in 'server.options.ca' configuration. Path to an SSL CA certificate or content of an SSL CA certificate.
  --server-options-cert <value...>                    Path to an SSL certificate or content of an SSL certificate.
  --server-options-cert-reset                         Clear all items provided in 'server.options.cert' configuration. Path to an SSL certificate or content of an SSL certificate.
  --server-options-crl <value...>                     Path to PEM formatted CRLs (Certificate Revocation Lists) or content of PEM formatted CRLs (Certificate Revocation Lists).
  --server-options-crl-reset                          Clear all items provided in 'server.options.crl' configuration. Path to PEM formatted CRLs (Certificate Revocation Lists) or content of PEM formatted CRLs (Certificate Revocation Lists).
  --server-options-key <value...>                     Path to an SSL key or content of an SSL key.
  --server-options-key-reset                          Clear all items provided in 'server.options.key' configuration. Path to an SSL key or content of an SSL key.
  --server-options-pfx <value...>                     Path to an SSL pfx file or content of an SSL pfx file.
  --server-options-pfx-reset                          Clear all items provided in 'server.options.pfx' configuration. Path to an SSL pfx file or content of an SSL pfx file.
  --static [value...]                                 Allows to configure options for serving static files from directory (by default 'public' directory).
  --no-static                                         Disallows to configure options for serving static files from directory.
  --static-directory <value...>                       Directory for static contents.
  --static-public-path <value...>                     The static files will be available in the browser under this public path.
  --static-serve-index                                Tells dev server to use serveIndex middleware when enabled.
  --no-static-serve-index                             Does not tell dev server to use serveIndex middleware.
  --static-watch                                      Watches for files in static content directory.
  --no-static-watch                                   Does not watch for files in static content directory.
  --static-reset                                      Clear all items provided in 'static' configuration. Allows to configure options for serving static files from directory (by default 'public' directory).
  --static-public-path-reset                          Clear all items provided in 'static.publicPath' configuration. The static files will be available in the browser under this public path.
  --watch-files <value...>                            Allows to configure list of globs/directories/files to watch for file changes.
  --watch-files-reset                                 Clear all items provided in 'watchFiles' configuration. Allows to configure list of globs/directories/files to watch for file changes.
  --no-web-socket-server                              Disallows to set web socket server and options.
  --web-socket-server-type <value>                    Allows to set web socket server and options (by default 'ws').

Global options:
  --color                                             Enable colors on console.
  --no-color                                          Disable colors on console.
  -v, --version                                       Output the version number of 'webpack', 'webpack-cli' and 'webpack-dev-server' and commands.
  -h, --help [verbose]                                Display help for commands and options.

To see list of all supported commands and options run 'webpack --help=verbose'.

Webpack documentation: https://webpack.js.org/.
CLI documentation: https://webpack.js.org/api/cli/.
Made with ♥ by the webpack team.

[!NOTE]

Detailed documentation for above options is available on this link.

With NPM Scripts

NPM package.json scripts are a convenient and useful means to run locally installed binaries without having to be concerned about their full paths. Simply define a script as such:

{
  "scripts": {
    "serve": "webpack serve"
  }
}

And run the following in your terminal/console:

npm run serve

NPM will automatically refer to the the binary in node_modules for you, and execute the file or command.

With the API

While it's recommended to run webpack-dev-server via the CLI, you may also choose to start a server via the API.

See the related API documentation for webpack-dev-server.

With TypeScript

If you use TypeScript in the webpack config, you'll need to properly type devServer property in order to avoid TS errors (e.g. 'devServer' does not exist in type 'Configuration'). For that use either:

/// <reference path="node_modules/webpack-dev-server/types/lib/Server.d.ts"/>
import type { Configuration } from "webpack";

// Your logic

Or you can import the type from webpack-dev-server, i.e.

import type { Configuration as DevServerConfiguration } from "webpack-dev-server";
import type { Configuration } from "webpack";

const devServer: DevServerConfiguration = {};
const config: Configuration = { devServer };

// module.exports
export default config;

The Result

Either method will start a server instance and begin listening for connections from localhost on port 8080.

webpack-dev-server is configured by default to support live-reload of files as you edit your assets while the server is running.

See the documentation for more use cases and options.

Browser Support

While webpack-dev-server transpiles the client (browser) scripts to an ES5 state, the project only officially supports the last two versions of major browsers. We simply don't have the resources to support every whacky browser out there.

If you find a bug with an obscure / old browser, we would actively welcome a Pull Request to resolve the bug.

Support

We do our best to keep issues in the repository focused on bugs, features, and needed modifications to the code for the module. Because of that, we ask users with general support, "how-to", or "why isn't this working" questions to try one of the other support channels that are available.

Your first-stop-shop for support for webpack-dev-server should be the excellent documentation for the module. If you see an opportunity for improvement of those docs, please head over to the webpack.js.org repo and open a pull request.

From there, we encourage users to visit the webpack discussions and talk to the fine folks there. If your quest for answers comes up dry in chat, head over to StackOverflow and do a quick search or open a new question. Remember; It's always much easier to answer questions that include your webpack.config.js and relevant files!

If you're twitter-savvy you can tweet #webpack with your question and someone should be able to reach out and lend a hand.

If you have discovered a :bug:, have a feature suggestion, or would like to see a modification, please feel free to create an issue on Github. Note: The issue template isn't optional, so please be sure not to remove it, and please fill it out completely.

Contributing

We welcome your contributions! Please have a read of CONTRIBUTING.md for more information on how to get involved.

Attribution

This project is heavily inspired by peerigon/nof5.

License

MIT