question-mark
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.

Is this the bug of react-error-overlay?

See original GitHub issue

Describe the bug

When I change the code and emit the hot-reload, there is iframe cover the whole page and report Uncaught ReferenceError: process is not defined.

image

image

image

image

Did you try recovering your dependencies?

Yes. It wasn’t happened before I recover my dependencies. After I recover my dependencies(remove node_module / package-lock.json and reinstall the dependencies), the problem has been there.

Which terms did you search for in User Guide?

Uncaught ReferenceError: process is not defined hot-reload webpackHotDevClient "win32"===process.platform

Environment

Environment Info:

current version of create-react-app: 4.0.3 running from /Users/xxx/.config/yarn/global/node_modules/create-react-app

System: OS: macOS Mojave 10.14.3 CPU: (8) x64 Intel® Core™ i7-4870HQ CPU @ 2.50GHz Binaries: Node: 11.6.0 - /usr/local/bin/node Yarn: 1.22.17 - /usr/local/bin/yarn npm: 6.5.0 - /usr/local/bin/npm Browsers: Chrome: 96.0.4664.110 Edge: Not Found Firefox: 94.0.2 Safari: 12.0.3 npmPackages: react: 16.12.0 => 16.12.0 react-dom: 16.12.0 => 16.12.0 react-scripts: ^4.0.3 => 4.0.3 npmGlobalPackages: create-react-app: Not Found

(paste the output of the command here.)

Steps to reproduce

  1. Reinstall the node_modules.
  2. npm start
  3. Change some code(maybe less) and error has been there.

Expected behavior

Console will not report the Uncaught ReferenceError: process is not defined and there is no iframe cover the page.

Actual behavior

Console reports the Uncaught ReferenceError: process is not defined and there is the iframe cover the page.

Reproducible demo

I will try to reproduce the demo later when I’m free, report the problem at first.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:166
  • Comments:86 (2 by maintainers)

github_iconTop GitHub Comments

136reactions
bknifflercommented, Dec 16, 2021

Sorry, the “workaround” still blocked the screen, though the errow was muted. What REALLY helped was putting a fixed version of react-error-overlay into devDependencies like:

"react-error-overlay": "6.0.9",
69reactions
ihorbondcommented, Jan 20, 2022

2 steps to resolve:

  1. Delete react.
  2. Install vue. Problem solved 😃
Read more comments on GitHub >

github_iconTop Results From Across the Web

create react app - Disable error overlay in development mode
The error overlay can be disabled by using the stopReportingRuntimeErrors helper utility in the react-error-overlay package.
Read more >
react-error-overlay - npm
react-error-overlay is an overlay which displays when there is a runtime error. Development. When developing within this package, make sure you ...
Read more >
How to get an error overlay with React Hot Loader - Jakob Lind
How to enable react error overlay for React Hot Loader. First, make sure you are using version 2.2.1 of webpack-dev-server. If you don't,...
Read more >
react-error-overlay | Yarn - Package Manager
react -error-overlay is an overlay which displays when there is a runtime error. Development. When developing within this package, make sure you run...
Read more >
Parcel v2.6.0
Both the React runtime error overlay and Parcel's build error overlay now support clicking on file names or line numbers in code frames...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found