Bump karma-webpack to ^5.0.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
karma-webpack	^5.0.0 -> ^5.0.1

---

Release Notes

webpack-contrib/karma-webpack (karma-webpack)

v5.0.1

Compare Source

Fixes

• security fixes

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for base-ui ready!

Name	Link
🔨 Latest commit	df75e66
🔍 Latest deploy log	https://app.netlify.com/sites/base-ui/deploys/65de0af3a0348f000884cf1d
😎 Deploy Preview	https://deploy-preview-104--base-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Waiting for the first build to start…

[michaldudak]

Similarly to mui/material-ui#40929, TextareaAutosize tests started to fail after this update.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[michaldudak]

@ZeeshanTamboli, I was hoping #189 would fix this PR, but it doesn't seem so. Would you like to take a look at this since you already have the context of TextareaAutosize?
It's not urgent, though.

[ZeeshanTamboli]

@michaldudak Using requestAnimationFrame in production, as indicated in the code comment, resolves the issue. However, I'm unclear why this resolves the issue now and why it failed previously. Additionally, I'm unsure what changes between versions 5.0.0 and 5.0.1 triggered this browser error.

[michaldudak]

Good catch!
I also don't know exactly what changes in 5.0.1 trigger this. This release was mostly about bumping the dependencies, so it could be any of the transitive deps causing this issue.
I've noticed that now karma tests behave more correctly (for example, they now fail when Popper's anchor is not added to the document), and this leads me to believe there were improvements introduced.