8.3 Breaking change

[mantysalo]

Prerequisites

• Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
• Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
• 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
• Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description

Not sure if mocha follows semver but #4543 introduced a breaking change as the version of yargs that was upgraded to does not support Node 8. Support was dropped in version 16.

Steps to Reproduce

1. Use Node 8
2. Try to run mocha

Expected behavior:

Mocha will run tests or show a warning of

Warning: Could not find any test files matching pattern: test
No test files found

if no test files are found

Actual behavior:
Mocha won't start when trying run with Node 8 and throws an error saying:

yargs parser supports a minimum Node.js version of 10. Read our version support policy: https://github.com/yargs/yargs-parser#supported-nodejs-versions

Reproduces how often: [What percentage of the time does it reproduce?]

100%

Versions

• The output of mocha --version and node node_modules/.bin/mocha --version: No output as it shows the yargs error, but I'm using version 8.3.0
• The output of node --version: 8.4.0
• Your operating system
  • name and version: MacOS
  • architecture (32 or 64-bit): 64bit
• Your shell (e.g., bash, zsh, PowerShell, cmd): bash

[mantysalo]

I did not initially notice by grepping the changelog that version 8 support was dropped.