Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migrate plugin for Webpack dev server v4

See original GitHub issue

Edited by maintainer: If you need support for WDS v4, please use the 0.5.0 releases.

Issue Analytics

State:
Created 2 years ago
Reactions:10
Comments:34 (11 by maintainers)

Top GitHub Comments

15reactions

t6adevcommented, Aug 19, 2021

Hi, I’m also facing the same issue. Temporarily, I set it like below to avoid the error.

new ReactRefreshWebpackPlugin({
  overlay: false,
})

Packages are,

"@pmmmwh/react-refresh-webpack-plugin": "^0.4.3",
"webpack": "^5.50.0",
"webpack-dev-server": "^4.0.0",

15reactions

pmmmwhcommented, Aug 19, 2021

0.5.0-rc.4 should work with WDS v4 by default, the socket path however would need a bit of re-work - ideally we would want to support both v3 and v4

Top Results From Across the Web

webpack-dev-server/migration-v4.md at master - GitHub

This document serves as a migration guide for webpack-dev-server@4.0.0 . ... v4 automatically apply HotModuleReplacementPlugin plugin when you set hot: true ...

To v4 from v3 - webpack

To v4 from v3 · Node.js v4 · CLI. The CLI has moved to a separate package: webpack-cli. · Update plugins. Many 3rd...

To v5 from v4 - webpack

This guide aims to help you migrating to webpack 5 when using webpack directly. If you are using a higher level tool to...

DevServer - webpack

This page describes the options that affect the behavior of webpack-dev-server (short: dev-server) version >= 4.0.0. Migration guide from v3 to v4 can...

DevServer - webpack

Allows dev-server to register custom mime types. The object is passed to the underlying webpack-dev-middleware . See documentation for usage notes. webpack.