react-scripts 3.3.0 / 3.3.1 -> [HMR] Waiting for update signal from WDS... in console (Edge not working still)

Describe the bug

I am pretty new to React, so bear with me please. I tried setting up a new project in react and these are the default dependencies generated in package.json :

“react”: “^16.12.0”, “react-dom”: “^16.12.0”, “react-scripts”: “3.3.0”

After I run npm start I get a message in the console “[HMR] Waiting for update signal from WDS…”

The page still shows up and refreshes automatically whenever a change is made but it only works on Chrome and Mozilla.

For some reason Microsoft Edge doesn’t work anymore even though it did before

Did you try recovering your dependencies?

I tried going back to different versions of react or scripts and everything goes back to normal when I have : “react”: “^16.12.0”, “react-dom”: “^16.12.0”, “react-scripts”: “3.3.0-next.62”

Everything above "react-scripts": "3.3.0-next.62" gives the error in the console and Edge stops working.

Which terms did you search for in User Guide?

I tried npm run eject to configure the webpack.config but I am not really that experienced and couldn’t see a problem

Environment

System: OS: Windows 10 10.0.18363 CPU: (4) x64 Intel® Core™ i5-7500 CPU @ 3.40GHz Binaries: Node: 10.16.3 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.13.3 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: 44.18362.449.0 Internet Explorer: 11.0.18362.1 npmPackages: react: ^16.12.0 => 16.12.0 react-dom: ^16.12.0 => 16.12.0 react-scripts: 3.3.0 => 3.3.0 npmGlobalPackages: create-react-app: Not Found

Steps to reproduce

(Write your steps here:)

1. npx create-react-app [NAME]
2. npm start
3. open console in browser

Expected behavior

No message in console. Microsoft Edge to show page.

Actual behavior

Message in console. Blank Page in Edge.

Edge with react-script: 3.3.0:

Edge with react-scripts: 3.3.0-next.62:

Chrome with react-script: 3.3.0 :

Chrome with react-scripts: 3.3.0-next.62:

Reproducible demo

https://github.com/Dodobrat/react-scripts-error

[jwandekoken]

I’m also experiencing the issue, the message just sits there at the console, but everything seems to be working

[seanfisher]

The one-liner temporary very hacky fix is to run the following in Git Bash:

sed --in-place -e "66a\    slashes: true," ./node_modules/react-dev-utils/webpackHotDevClient.js

This will add in slashes: true to line 66 of the ./node_modules/react-dev-utils/webpackHotDevClient.js file