webpack-dev-server

Developer Tools

Development server with live reloading for webpack projects.

Latest v6.0.0 · by webpackWebsitewebpack/webpack-dev-server

Release activity

Release activity — 5 releases across 5 days in the last year. Each cell is one day; darker means more releases that day. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on May 3, 2026No releases on May 10, 2026No releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026No releases on Aug 16, 2026
MondayNo releases on May 4, 20261 release on May 11, 2026No releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026No releases on Aug 17, 2026
TuesdayNo releases on May 5, 2026No releases on May 12, 2026No releases on May 19, 2026No releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 2026No releases on Jul 28, 2026No releases on Aug 4, 2026No releases on Aug 11, 2026No releases on Aug 18, 2026
WednesdayNo releases on May 6, 2026No releases on May 13, 2026No releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026No releases on Aug 12, 2026No releases on Aug 19, 2026
ThursdayNo releases on May 7, 2026No releases on May 14, 2026No releases on May 21, 2026No releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 20261 release on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026No releases on Aug 13, 2026
FridayNo releases on May 8, 2026No releases on May 15, 2026No releases on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 20261 release on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 20261 release on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026No releases on Aug 14, 2026
SaturdayNo releases on May 9, 2026No releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026No releases on Aug 15, 2026

5 releases in the last year

Changelog

v6.0.0

Latest
Added 1
  • Add plugin support to webpack-dev-server for integrating with the compiler lifecycle
Changed 10
  • Bump Express to v5
  • Bump the webpack peer dependency range from ^5.0.0 to ^5.101.0
  • Convert the source to native ES modules with both ESM and CommonJS builds via the exports field
  • Update http-proxy-middleware to v4
  • Update webpack-dev-middleware to v8 and make server.middleware.getFilenameFromUrl() asynchronous
  • Enable the compression middleware for HTTP/2 connections
Fixed 1
  • Treat loopback aliases as equivalent in isSameOrigin so the WebSocket client does not reject valid same-origin connections
Removed 7
  • Drop support for Node.js < 22.15.0
  • Remove CLI flags
  • Remove the internalIP and internalIPSync static methods from Server
  • Remove the bypass option from proxy configuration
  • Remove SockJS support from the webSocketServer option
  • Remove the spdy dependency
  • Remove the colorette dependency in favor of native ANSI styling
Security 1
  • Reject cross-site requests to the internal open-editor and invalidate endpoints requiring same-origin validation

From webpack-dev-server

Major Changes
  • Bump Express to v5. See the Express 5 migration guide for the full list of breaking changes. (by @bjohansebas in #5674)

  • Bump the webpack peer dependency range from ^5.0.0 to ^5.101.0. (by @bjohansebas in #5674)

  • Drop support for Node.js < 22.15.0. (by @bjohansebas in #5674)

  • Convert the source to native ES modules. The package keeps "type": "module" and now exposes both an ESM and a CommonJS build via the exports field: ESM consumers import the native lib/, while CommonJS consumers require() a transpiled dist/ build, allowing the package to be consumed from both ESM and CommonJS without relying on require(ESM) for CommonJS consumers. (by @bjohansebas in #5674)

  • Remove CLI flags. Use the serve command from webpack-cli together with a configuration file or the programmatic API instead. (by @bjohansebas in #5674)

  • Remove the internalIP and internalIPSync static methods from Server. Resolve the local IP yourself if you need it. (by @bjohansebas in #5674)

  • Remove the bypass option from proxy configuration. Use the router or context options provided by http-proxy-middleware instead. (by @bjohansebas in #5674)

  • Remove SockJS support. The webSocketServer option no longer accepts "sockjs"; use the default "ws" transport instead. (by @bjohansebas in #5674)

  • Remove the spdy dependency. Use the built-in node:http2 module via the server option for HTTP/2 support. (by @bjohansebas in #5674)

  • Update http-proxy-middleware to v4. See the http-proxy-middleware v3 release notes and v4 release notes for the full list of breaking changes. (by @bjohansebas in #5674)

  • Update webpack-dev-middleware to v8 and sync originalUrl for middleware compatibility. server.middleware.getFilenameFromUrl() is now asynchronous and resolves to { filename, extra: { stats, outputFileSystem } }. See the webpack-dev-middleware v8 release notes for details. (by @bjohansebas in #5674)

Minor Changes
  • Add plugin support. webpack-dev-server can now be used as a webpack plugin, integrating with the compiler lifecycle without explicitly passing a compiler, preventing multiple server starts on recompilation, ensuring clean shutdown, and supporting MultiCompiler setups with multiple independent plugin servers. (by @bjohansebas in #5674)

  • Enable the compression middleware for HTTP/2 connections. (by @bjohansebas in #5674)

  • Remove the colorette dependency in favor of native ANSI styling. (by @bjohansebas in #5674)

  • Update chokidar to v5 and extend watchFiles.options.ignored to support glob string patterns via tinyglobby. (by @bjohansebas in #5674)

  • Use compiler.platform to determine the target environment instead of inspecting the resolved target string. Universal targets ("universal" or ["web", "node"], where compiler.platform.universal is true since webpack 5.108.0) are treated as web targets so the client runtime is injected. (by @bjohansebas in #5674)

  • Use the WHATWG URL API instead of the deprecated url.parse. (by @bjohansebas in #5674)

Patch Changes
  • Bump production dependencies, notably open to v11 and p-retry to v8. (by @bjohansebas in #5674)

  • Reject cross-site requests to the internal open-editor and invalidate endpoints. They performed state-changing actions (opening a file in the editor, forcing a recompilation) on any GET request, so a page the developer visited could trigger them. They now require a same-origin request, validated via Sec-Fetch-Site with an Origin/Host fallback. (by @bjohansebas in #5691)

  • Treat loopback aliases (127.0.0.1, ::1, localhost) as equivalent in isSameOrigin so the WebSocket client does not reject valid same-origin connections. (by @bjohansebas in #5674)

  • Migrate the test suite from Jest to node:test and set up the jsdom environment. (by @bjohansebas in #5674)

  • Update webpack-cli to v7.0.2. (by @bjohansebas in #5674)

View originalPermalink
How v6.0.0 went

v5.2.6

Fixed 2
  • Allow `undefined` as the `Server` constructor `options` argument, defaulting it to `{}`
  • Handle malformed `Host` and `Origin` header values gracefully when validating requests
Security 1
  • Protect the built-in state-changing routes (`/webpack-dev-server/invalidate` and `/webpack-dev-server/open-editor`) against cross-site request forgery by checking requests with `Sec-Fetch-Site` header or `Origin`/`Host` comparison

From webpack-dev-server

Patch Changes
  • fix: allow undefined as the Server constructor options argument again (by @bjohansebas in #5695)

    Restores accepting undefined (defaulting it to {}) for the options argument, so passing a webpack config's optional devServer field type-checks and works as before.

  • Protect the built-in state-changing routes (/webpack-dev-server/invalidate and /webpack-dev-server/open-editor) against cross-site request forgery. Requests are now checked with Sec-Fetch-Site (falling back to an Origin/Host comparison when it is absent), so a cross-site page can no longer trigger a rebuild or open a file in the editor. Same-origin requests, user-initiated navigations, and non-browser clients (e.g. curl) are unaffected. (by @bjohansebas in #5698)

  • Handle malformed Host and Origin header values gracefully when validating requests. (by @bjohansebas in #5699)

View originalPermalink
How v5.2.6 went

v5.2.5

Fixed 1
  • Skip the HMR WebSocket path when forwarding upgrade requests to user-defined proxies, so custom proxy WebSocket upgrades are no longer intercepted by the dev server

From webpack-dev-server

Patch Changes
  • Skip the HMR WebSocket path when forwarding upgrade requests to user-defined proxies, so custom proxy WebSocket upgrades are no longer intercepted by the dev server. (by @bjohansebas in #5680)
View originalPermalink
How v5.2.5 went

v5.2.4

Fixed 1
  • set Cross-Origin-Resource-Policy header to prevent source code theft over HTTP

From webpack-dev-server

5.2.4 (2026-05-11)
Bug Fixes
  • set Cross-Origin-Resource-Policy header to prevent source code theft over HTTP
View originalPermalink
How v5.2.4 went

v5.2.3

Changed 1
  • Upgrade selfsigned to v5
Fixed 4
  • Add `cause` for `errorObject`
  • Fix compatibility with event target and universal target and lazy compilation
  • Add ESC key to dismiss overlay
  • Fix progress indicator styles

From webpack-dev-server

5.2.3 (2026-01-12)
Bug Fixes
  • add cause for errorObject (#5518) (37b033d)
  • compatibility with event target and universal target and lazy compilation (574026c)
  • overlay: add ESC key to dismiss overlay (#5598) (f91baa8)
  • progress indicator styles (#5557) (41a53a1)
  • upgrade selfsigned to v5
View originalPermalink
How v5.2.3 went

v5.2.2

Fixed 4
  • Fix "Overlay enabled" false positive
  • Prevent crash when error is null for runtime errors
  • Remove unnecessary header X_TEST
  • Respect the allowedHosts option for cross-origin header check

From webpack-dev-server

5.2.2 (2025-06-03)
Bug Fixes
  • "Overlay enabled" false positive (18e72ee)
  • do not crush when error is null for runtime errors (#5447) (309991f)
  • remove unnecessary header X_TEST (#5451) (64a6124)
  • respect the allowedHosts option for cross-origin header check (#5510) (03d1214)
View originalPermalink
How v5.2.2 went

v5.2.1

Fixed 2
  • Prevent overlay for errors caught by React error boundaries
  • Take the first network found instead of the last one to restore the same behavior as 5.0.4
Security 2
  • Cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
  • Requests with IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or if different from the Host header

From webpack-dev-server

5.2.1 (2025-03-26)
Security
  • cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
  • requests with an IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or it different from the Host header

The above changes may make the dev server not work if you relied on such behavior, but unfortunately they carry security risks, so they were considered as fixes.

Bug Fixes
  • prevent overlay for errors caught by React error boundaries (#5431) (8c1abc9)
  • take the first network found instead of the last one, this restores the same behavior as 5.0.4 (#5411) (ffd0b86)
View originalPermalink
How v5.2.1 went

v5.2.0

Added 1
  • Add `getClientEntry` and `getClientHotEntry` methods to get client entries
Fixed 1
  • Speed up initial client bundling

From webpack-dev-server

5.2.0 (2024-12-11)
Features
  • added getClientEntry and getClientHotEntry methods to get clients entries (dc642a8)
Bug Fixes
  • speed up initial client bundling (145b5d0)
View originalPermalink
How v5.2.0 went

v5.1.0

Added 4
  • Add visual progress indicators
  • Add the `app` option to be `Function` (by default only with `connect` compatibility frameworks)
  • Allow the `server` option to be `Function`
  • Add HTTP2 support for `connect` and `connect` compatibility frameworks which support HTTP2
Fixed 5
  • Check the `platform` property to determinate the target
  • Fix IPv6 output
  • Replace `rimraf` with `rm`
  • Replace default gateway
  • Support `devServer: false`

From webpack-dev-server

5.1.0 (2024-09-03)
Features
  • add visual progress indicators (a8f40b7)
  • added the app option to be Function (by default only with connect compatibility frameworks) (3096148)
  • allow the server option to be Function (#5275) (02a1c6d)
  • http2 support for connect and connect compatibility frameworks which support HTTP2 (#5267) (6509a3f)
Bug Fixes
View originalPermalink
How v5.1.0 went

v4.15.2

Security 1
  • Bump webpack-dev-middleware

From webpack-dev-server

4.15.2 (2024-03-20)
Bug Fixes
  • security: bump webpack-dev-middleware (4116209)
View originalPermalink
How v4.15.2 went
View all

Discussion

If you publish webpack-dev-server, you can claim this product by proving you administer its repository.