chore(deps): update dev dependencies (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	22.19.17 → 24.13.2
concurrently	9.2.1 → 10.0.3

---

Release Notes

open-cli-tools/concurrently (concurrently)

v10.0.3

Compare Source

Republish of https://github.com/open-cli-tools/concurrently/releases/tag/v10.0.1 with Trusted Publishing enabled (see #​595)

Full Changelog: open-cli-tools/concurrently@v10.0.2...v10.0.3

v10.0.1

Compare Source

• Ensure FlowController type is exported - #​594

Full Changelog: open-cli-tools/concurrently@v10.0.0...v10.0.1

v10.0.0

Compare Source

💥 Breaking Changes

• Dropped support for Node.js <22.0.0.
  Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.
• concurrently is now ESM-only.
  It's now possible to require(esm). See here for interoperability.
• Prefix colors now default to automatic - #​581
  The colors used to default to reset (which does nothing). Concurrently now automatically selects a color, out of the box.
  The list of colors used is not jarring nor carries semantic meaning, and reads well in both dark and light terminal backgrounds.
• Removed deprecated flags and options
  • CLI flag --name-separator: use commas instead.
  • API option killOthers: use killOthersOn instead.

✨ New Features

• Support applying modifiers to hex prefix colors (e.g. #ff0000.bold) - #​450
• Support chalk's color functions in prefixes (e.g. rgb(), hex(), bgRgb(), etc) - #​578
• Set prefix background color via bg#RRGGBB - #​578
• Allow shell override via --shell CLI flag/shell API option - #​288, #​589, #​556
  concurrently distinguishes between cmd.exe, powershell, and POSIX-based shells.
• Manual prefix coloring in templates e.g. [{color}{name}{/color}] - #​583, #​587

🐛 Bug fixes

• Scope quote normalization to CLI input - #​582, #​585
  It should now also be possible to run commands like "/some/command" foo bar"
• Don't throw when color doesn't exist - #​580

🔐 Security

• Address vulnerability in shellquote - #​591

Other changes

• Warn about running on Snap - #​584

New Contributors

• @​philfreo made their first contribution in #​566
• @​garretmh made their first contribution in #​450
• @​CodeF53 made their first contribution in #​574
• @​nkappler made their first contribution in #​577
• @​stephanschubert made their first contribution in #​578
• @​GermanJablo made their first contribution in #​581
• @​y-nk made their first contribution in #​587
• @​samchungy made their first contribution in #​591
• @​saito-netartz made their first contribution in #​590
• @​jeffrey-takuma made their first contribution in #​585

Full Changelog: open-cli-tools/concurrently@v9.2.1...v10.0.0

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "before 4am on Monday"
• 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.

👻 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.

[doistbot]

This PR updates development dependencies to their latest major versions.

Few things worth tightening:

• Revert @types/node to v22 to match the .nvmrc target and prevent type-checking from passing on unsupported APIs.
• Either hold concurrently at v9 or raise the project's declared Node minimum, since v10 drops support for Node <22.

_{Share Feedback • Review Logs}

[doistbot]

🟡 P2 This updates @types/node to 24.x, but .nvmrc targets Node v22. Since major versions of @types/node map to Node.js major versions, upgrading this before the runtime could lead to successful type-checks for Node 24 APIs that will crash at runtime on Node 22. Consider keeping @types/node on 22.x until the runtime target is updated.

[doistbot]

🟡 P2 concurrently v10 drops support for Node <22, so this change breaks the documented local-dev flow (npm run dev) for contributors still on the repo's stated Node 18+ minimum. Either keep concurrently on v9 here, or raise the project's declared Node floor in the same PR so the supported environment matches the toolchain.