jest: Unrecognized cli patterns for jest@beta

πŸ› Bug Report

Multiple users are reporting the following error when trying jest@beta:

Unrecognized CLI Parameters:

  Following options were not recognized:
  ["changed-files-with-ancestor", "clear-cache", "clear-mocks", "collect-coverage", "detect-leaks", "detect-open-handles", "error-on-deprecated", "find-related-tests", "force-exit", "last-commit", "list-tests", "log-heap-usage", "map-coverage", "no-stack-trace", "only-changed", "only-failures", "pass-with-no-tests", "reset-mocks", "reset-modules", "restore-mocks", "run-in-band", "run-tests-by-path", "show-config", "skip-filter", "test-location-in-results", "update-snapshot", "use-stderr", "watch-all", "notify-mode", "prettier-path"]

  CLI Options Documentation:
  https://jestjs.io/docs/en/cli.html

To Reproduce

I am unable to repro but the steps seem to be to install and run jest@beta

@onetom @SerhiiBilyk and @bcanseco all reported the same issue in https://github.com/facebook/jest/issues/7382

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 5
  • Comments: 18 (16 by maintainers)

Commits related to this issue

Most upvoted comments

was that fix released in a patch?

It was released in a patch version of yargs: 12.0.3 to be exact: https://github.com/yargs/yargs/compare/v12.0.2..v12.0.3#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R32

We should have B, but the object we get back from yargs should only have the camelCase ones, so we don’t have multiple sources of truth