Bug description
For some time when in a dev environment with npm run dev-server and Firefox, some actions cause the webpack overlay to show error in multiple parts of the app. Here's a consistent reproduction:
(Using firefox in dev-server)
- Go to any dashboard
- Edit dashboard
- Change dashboard name
- You will see the error appear.
ERROR
can't access property "stack", error is undefined
createOverlay/<@webpack-internal:///./node_modules/webpack-dev-server/client/overlay.js:608:11
It doesn't cause any issues so you can close the overlay and continue working but the error will continue to appear.
Workarounds
Setting
overlay: {
errors: false,
warnings: false,
runtimeErrors: false,
},
in webpack.config.js sidesteps the issue by not creating an overlay
Screenshots/recordings
Firefox:
https://github.com/user-attachments/assets/053735e3-a76f-4d10-84e9-46bca42f4ace
Chrome:
https://github.com/user-attachments/assets/64e5f2a4-f143-4d7c-83f6-1000a16a716e
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Firefox
Additional context
In Chrome error still happens but the overlay is not shown and is less disruptive.
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This error comes from the webpack-dev-server overlay and is not caused by Superset's code or configuration. The overlay settings in Superset are generic and do not differentiate between browsers; the difference in behavior between Firefox and Chrome is due to how webpack-dev-server and the browsers themselves handle errors, not anything specific to Superset. Disabling the overlay in webpack.config.js (your current workaround) will suppress the error display but won't address the underlying issue. There are no existing Superset tickets or docs about this, and no targeted workaround or patch for this specific overlay error in Firefox is documented in the codebase or recent PRs. Keeping dependencies up to date may help if an upstream fix is released, so it's worth monitoring the webpack-dev-server project for related issues or updates.
Reference: webpack.config.js overlay config
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
