chore!: drop support for node v20

[Shinigami92]

• Drop support for Node v20 (EOL)
• Drop support for es2023 (new target is es2024 as minimum fully covered by Node v22.13)

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	06045bc
🔍 Latest deploy log	https://app.netlify.com/projects/fakerjs/deploys/6a6a434ade1f0c00084c7240
😎 Deploy Preview	https://deploy-preview-3916.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.91%. Comparing base (e59f499) to head (06045bc).

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #3916   +/-   ##
=======================================
  Coverage   98.91%   98.91%           
=======================================
  Files         924      924           
  Lines        3224     3224           
  Branches      567      585   +18     
=======================================
  Hits         3189     3189           
  Misses         31       31           
  Partials        4        4           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ST-DDT]

FYI:

faker/test/scripts/apidocs/verify-jsdoc-tags.spec.ts

Line 81 in e0223a7

// eslint-disable-next-line unicorn/prefer-iterator-to-array -- Requires Node 22+

• chore(deps): update eslint (major) #3914

[matthewmayer]

Can i suggest we use a similar pattern for what we did in v9 and where there are breaking changes queued up for v11 we add something like

docs/guide/upgrading_v11/3916.md

with a snippet explaining the breaking change. This will make writing the v11 upgrading guide easier.

[xDivisionByZerox]

You don't need to suggest it. You can simply point at our own contributions guidelines:

• https://github.com/faker-js/faker/blob/next/CONTRIBUTING.md#L202

[Shinigami92]

Can i suggest we use a similar pattern for what we did in v9 and where there are breaking changes queued up for v11 we add something like

docs/guide/upgrading_v11/3916.md

with a snippet explaining the breaking change. This will make writing the v11 upgrading guide easier.

Thanks for the reminder 👍