chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	4b4cde9
🔍 Latest deploy log	https://app.netlify.com/projects/fakerjs/deploys/6a0f407535ab20000865d1aa
😎 Deploy Preview	https://deploy-preview-3848.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 (8b4e2b1) to head (4b4cde9).

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #3848   +/-   ##
=======================================
  Coverage   98.91%   98.91%           
=======================================
  Files         905      905           
  Lines        3146     3146           
  Branches      581      581           
=======================================
  Hits         3112     3112           
  Misses         30       30           
  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]

It looks like tsdown will drop support for node 20 soon.
Unrun (used by tsdown or somewhere alongside it) already dropped support for node 20.

[Shinigami92]

It looks like tsdown will drop support for node 20 soon. Unrun (used by tsdown or somewhere alongside it) already dropped support for node 20.

should we wait for v11? I think we should drop node v20 support in a major

[xDivisionByZerox]

should we wait for v11? I think we should drop node v20 support in a major

From my understanding this is only for the local dev setup. The dev container already puts dev in a node 24 environments. The only "gotcha" could be our documentation stating that all LTS versions are fine:

faker/docs/contributing/set-up-a-development-environment.md

Line 44 in 8b4e2b1

1. Ensure you have [the current LTS version of Node.js](https://nodejs.org/en/download) installed.

But since v20 is EOL ad not LTS anymore, that should also be fine.

[Shinigami92]

Ah ok, so it still supports transpiling down to node v20? it's just the dev env where you need to compile it?

[xDivisionByZerox]

Ah ok, so it still supports transpiling down to node v20? it's just the dev env where you need to compile it?

Correct. You might need to run tsdown with node v22 and up, but you can specify whatever target you want. From a quick look through the docs, you could, for example, still compile down to node12, although that was not specified in the engines.