Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

93
Views
Transparent iFrame blocks mouse event when using react-scripts start

Has anyone ever come across this issue?

When using react-scripts start, everything seems ok on first load. As soon as a change is made to a file, all the mouse event seem to stop working (can't click on buttons, inputs, no tooltips etc.), even though the browser appears to update.

If I refresh the page the events work again, until a file is changed.

This isn't a problem in production as the watcher isn't involved there.

Any ideas?

EDIT:
I've found the problem but I'm not sure what the solution is. It appears that a iFrame is added to the DOM when the watcher reloads. It looks like it has something to do with licenses. The body within the iFrame is empty but there is some minified JS with a comment on the top line:

/*! For license information please see iframe-bundle.js.LICENSE.txt */

Does anyone know how to prevent this iFrame appearing.

over 4 years ago · Santiago Trujillo
5 answers
Answer question

0

My solution npm install --save --save-exact react-scripts@5.0.0 then rm -rf node_module && rm -rf package-lock.json y then npm install and npm start =)

over 4 years ago · Santiago Trujillo Report

0

This works for me:

"react-error-overlay": "6.0.9",

and add the fixed dependency version to the resolutions section of your package.json:

"resolutions": {
  "//": "See https://github.com/facebook/create-react-app/issues/11773",
  "react-error-overlay": "6.0.9"
},
over 4 years ago · Santiago Trujillo Report

0

Upgrading to react-scripts v5 that way made it work for me :

npm i react-scripts@5.0.0
over 4 years ago · Santiago Trujillo Report

0

This is what fixed it for me:

npm upgrade react-scripts
over 4 years ago · Santiago Trujillo Report

0

You need to upgrade React-Scripts to latest version

npm install react-scripts@latest
over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!