Fix commander v14 duplicate flag conflict - rename Mocha debug to --inspect

[Copilot]

Motivation/Description of the PR

The upgrade from commander v11.1.0 to v14.0.2 introduced a breaking change where duplicate option flags are no longer allowed. This caused the error:

Error: Cannot add option '-d, --debug' to command 'run' due to conflicting flag '--debug'

Root Cause: Both the run and run-rerun commands had duplicate --debug options:

1. commandFlags.debug.flag adds --debug (CodeceptJS's debug flag for "output additional information")
2. -d, --debug adds it again (Mocha's debug flag for "enable node's debugger")

Solution: Renamed the Mocha debug flag from -d, --debug to --inspect to avoid conflict while preserving both functionalities. This allows users to:

• Use --debug for CodeceptJS debug output
• Use --inspect for Node debugger
• Use both flags together if needed for different log outputs

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium

Applicable plugins:

• allure
• autoDelay
• autoLogin
• customLocator
• pauseOnFail
• coverage
• retryFailedStep
• screenshotOnFail
• selenoid
• stepByStepReport
• stepTimeout
• wdio
• subtitles

Type of change

• 🔥 Breaking changes
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)

Original prompt

Investigate and fix issue of commander upgrading in the codebase. The error is throw new Error(Cannot add option '${option.flags}'${this._name && to command '${this._name}'`} due to conflicting flag '${matchingFlag}'

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[kobenguyent]

@copilot investigate and propose another approach to have debug flag for both node and codeceptjs and we sometimes want to see different logs

[Copilot]

@copilot investigate and propose another approach to have debug flag for both node and codeceptjs and we sometimes want to see different logs

I've renamed the Mocha debug flag from -d, --debug to --inspect to avoid the conflict. Now both debug flags are available:

• --debug - CodeceptJS debug output (additional information)
• --inspect - Node's debugger
• --debug-brk - Node's debugger breaking on first line

This allows you to use either flag independently or both together. Commit: a957813

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• jsonplaceholder.typicode.com
  • Triggering command: node /home/REDACTED/work/CodeceptJS/CodeceptJS/node_modules/.bin/mocha test/unit --recursive --timeout 10000 --reporter @testomatio/reporter/mocha (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)