The committers listed above are authorized under a signed CLA.

• ✅ login: negimox / name: Chetan Pandey (bae1180,7b8964c)

Hello,@alexander-akait@snitin315 can you verify if this solution for issue#5411 is appropriate?

Hello,@alexander-akait

Can you test using this repo -https://github.com/OliverJAsh/react-error-boundary-uncaught-issue/tree/webpack-dev-server like was written in the issue?

Yes, I have tested with the repo attached in the issue and it was working i.e. overlay doesn't show. For reference of the test you can check the .mp4 video under additional info where that repo is used.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.42%. Comparing base(af6bd68) to head(7b8964c).
Report is 108 commits behind head on master.

@@            Coverage Diff             @@##           master    #5431      +/-   ##==========================================- Coverage   90.29%   83.42%   -6.88%==========================================  Files          15       13       -2       Lines        1577     1979     +402       Branches      601      723     +122     ==========================================+ Hits         1424     1651     +227- Misses        140      295     +155- Partials       13       33      +20

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report?Share it here.

Let's fixlint error

Hello@alexander-akait, lint errors are resolved now

Hi@alexander-akait, apologies for the repeated mentions. I noticed that one of the checks is failing—specifically,Test - windows-latest - Node v20.x, Webpack latest (4/4). Based on the error log, it seems the failure is occurring in the test/e2e/api.test.js file for cases when the port is either null or undefined, resulting in the error: "listen EACCES: permission denied 0.0.0.0:60000." Could you please help clarify if these errors might be related to my changes in the client/overlay file?

Ignore it, this tests are unstable in some situations, if you want to rewrite tests - PR welcome, but it is not related to your changes in this PR, so I will merge

Did this update cause a regression for plain vanilla JS users? Everything was working fine in "webpack-dev-server": "~5.2.0", and now with 5.2.1, the overlay never shows, see this console error, which looks like the new code added:

overlay.js:602 Uncaught TypeError: Cannot read properties of null (reading 'stack')
at eval (overlay.js:602:1)

Once again, we don't use react. Just plain, plain as plain vanilla JS.

@cakidnyc Can you create reproducible test repo?

Reproduced, looks like your code throws null, i.e. throw null; I will fix it, but I recommended check out your code, because it is very strange to thrownull

Reproduced, looks like your code throws null, i.e. throw null; I will fix it, but I recommended check out your code, because it is very strange to thrownull

Thanks. I agree, but that error is coming from a 3rd party lib. To quote (almost) Forest Gump's Mom: "UI Dev is like a box of chocolates ... you never know what you are going to get".

Did this update cause a regression for plain vanilla JS users? Everything was working fine in "webpack-dev-server": "~5.2.0", and now with 5.2.1, the overlay never shows, see this console error, which looks like the new code added:

overlay.js:602 Uncaught TypeError: Cannot read properties of null (reading 'stack') at eval (overlay.js:602:1)

Once again, we don't use react. Just plain, plain as plain vanilla JS.

im having this problem currently, all typescript and react