Bump chokidar

[simhnna]

Bug Report Checklist

• I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
• I have searched for related issues and issues with the faq label, but none matched my issue.
• I have 'smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, my usage of Mocha, or Mocha itself.
• I want to provide a PR to resolve this

Expected

works with typescript

Actual

chokidar is incompatible to current @types/node releases
paulmillr/chokidar#1299

Minimal, Reproducible Example

Versions

mocha 10.4.0
@types/node 20.12.11
node 20.12.2

Additional Info

If #5114 was already done this wouldn't be an issue.

I'd just bump chokidar to ^3.6.0

[JoshuaKGoldberg]

Heya thanks for filing! I just marked #5114 as accepting PRs, so let's go with that one instead. That way we don't have to do raise the minimum version of chokidar, as that could arguably be considered a breaking change.

[simhnna]

I don't know why updating chokidar would be considered a breaking change. It's a direct dependency and not a peer dependency so mocha is free to use whatever version without compatibility issues with any other library. Also chokidar seems to be following semver and is so widely used that I doubt any breaking change makes it into a minor/patch release

[JoshuaKGoldberg]

If users happen to have their own dependency on chokidar then changing our version could cause a second version of it to appear in their node_modules. I've in the past been yelled at on the internet about bugs caused by introduced differing package versions.

+1 to your point that it doesn't seem very likely to be a real breaking change 😄. But figuring out whether chokidar version differences could cause these kinds of bugs is something I don't think we need to spend the time on given that #5114 would also solve the issue.