🛠 Repo: Replace fs-extra with newer fs built-ins

[JoshuaKGoldberg]

Tooling Suggestion Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• 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 want to provide a PR to resolve this

Overview

I ran eslint-plugin-depend on the Mocha repo. It had two reports about fs-extra:

/Users/josh/repos/mocha/test/integration/helpers.js
  5:12  error  "fs-extra" should be replaced with an alternative package. Read more here: https://github.com/es-tooling/module-replacements/blob/main/docs/modules/fs-extra.md  depend/ban-dependencies

/Users/josh/repos/mocha/test/integration/options/watch.spec.js
  3:12  error  "fs-extra" should be replaced with an alternative package. Read more here: https://github.com/es-tooling/module-replacements/blob/main/docs/modules/fs-extra.md  depend/ban-dependencies

Per https://github.com/es-tooling/module-replacements/blob/main/docs/modules/fs-extra.md:

fs-extra adds some file system methods that previously were not included in the native fs module and added Promise support to the fs methods.
Many of the fs-extra modules have since been implemented natively by Node.

Proposal: let's switch to native node:fs / node:fs/promises.

Additional Info

Note that both are within test/integration. This shouldn't impact users.

[ericcornelissen]

Hey - first time contributor here. I liked the idea of this kind of maintenance work and figured I could do this without reading the Contributing Guidelines but then I noticed the status: accepting prs¹ requirement.

Since this issue doesn't have that label yet but I already did the work, I'll just leave the changeset here: main...ericcornelissen:mocha:5266-fs-extra. Happy to open a PR if that's wanted 🙂

Footnotes

1. the link of which here seems to be incorrect btw. The text says status: accepting prs but points to the help-wanted label instead (which no longer exists) ↩

[JoshuaKGoldberg]

Thanks @ericcornelissen, much appreciated! I'd put it in status: in triage in case someone else from @mochajs/maintenance-crew has time to review and wants to put their own thoughts forward. They've both been pretty slammed with other things this year so I wouldn't be surprised if in a week or two this just defaults to status: accepting prs. At which point 👍 to your draft changeset becoming a PR.

the link of which here seems to be incorrect btw. The text says status: accepting prs but points to the help-wanted label instead (which no longer exists) ↩

Ha, good catch. Up for sending a PR? I think we can skip filing an issue for a quick docs typo like that. 🙂

[ericcornelissen]

[...] I wouldn't be surprised if in a week or two this just defaults to status: accepting prs. At which point 👍 to your draft changeset becoming a PR.

Thanks for clarifying the process. I'll keep an eye out for that and submit a PR when it switched 👍

Ha, good catch. Up for sending a PR? I think we can skip filing an issue for a quick docs typo like that. 🙂

Will do in just a moment 🙂

[JoshuaKGoldberg]

Ok @ericcornelissen I think we're good to go. Accepting PRs! 🚀