fix(deps): update dependency commander to v12

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
commander	11.0.0 -> 12.1.0

---

Release Notes

tj/commander.js (commander)

v12.1.0

Compare Source

Added

v12.0.0

Compare Source

Added

• .addHelpOption() as another way of configuring built-in help option ([#​2006])
• .helpCommand() for configuring built-in help command ([#​2087])

Fixed

• Breaking: use non-zero exit code when spawned executable subcommand terminates due to a signal ([#​2023])
• Breaking: check passThroughOptions constraints when using .addCommand and throw if parent command does not have .enablePositionalOptions() enabled ([#​1937])

Changed

• Breaking: Commander 12 requires Node.js v18 or higher ([#​2027])
• Breaking: throw an error if add an option with a flag which is already in use ([#​2055])
• Breaking: throw an error if add a command with name or alias which is already in use ([#​2059])
• Breaking: throw error when calling .storeOptionsAsProperties() after setting an option value ([#​1928])
• replace non-standard JSDoc of @api private with documented @private ([#​1949])
• .addHelpCommand() now takes a Command (passing string or boolean still works as before but deprecated) ([#​2087])
• refactor internal implementation of built-in help option ([#​2006])
• refactor internal implementation of built-in help command ([#​2087])

Deprecated

• .addHelpCommand() passing string or boolean (use .helpCommand() or pass a Command) ([#​2087])

Removed

• Breaking: removed default export of a global Command instance from CommonJS (use the named program export instead) ([#​2017])

Migration Tips

global program

If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new Command).

// const program = require('commander');
const { program } = require('commander');

option and command clashes

A couple of configuration problems now throw an error, which will pick up issues in existing programs:

• adding an option which uses the same flag as a previous option
• adding a command which uses the same name or alias as a previous command

v11.1.0

Compare Source

Fixed

• TypeScript: update OptionValueSource to allow any string, to match supported use of custom sources ([#​1983])
• TypeScript: add that Command.version() can also be used as getter ([#​1982])
• TypeScript: add null return type to Commands.executableDir(), for when not configured ([#​1965])
• subcommands with an executable handler and only a short help flag are now handled correctly by the parent's help command ([#​1930])

Added

• registeredArguments property on Command with the array of defined Argument (like Command.options for Option) ([#​2010])
• TypeScript declarations for Option properties: envVar, presetArg ([#​2019])
• TypeScript declarations for Argument properties: argChoices, defaultValue, defaultValueDescription ([#​2019])
• example file which shows how to configure help to display any custom usage in the list of subcommands ([#​1896])

Changed

• (developer) refactor TypeScript configs for multiple use-cases, and enable checks in JavaScript files in supporting editors ([#​1969])

Deprecated

• Command._args was private anyway, but now available as registeredArguments ([#​2010])

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: serialport-monorepo@0.0.0
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.8.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.8.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-22T23_56_03_292Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T23_56_03_292Z-debug-0.log