Merge remote-tracking branch 'origin/develop' into release/10.x

CHANGELOG.md

@@ -8,6 +8,18 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 <!-- markdownlint-disable MD024 -->
 <!-- markdownlint-disable MD004 -->
 
+## [9.4.1] (2022-09-30)
+
+### Fixed
+
+- `.setOptionValue()` now also clears option source ([#1795])
+- TypeScript: add `implied` to `OptionValueSource` for option values set by using `.implies()` ([#1794])
+- TypeScript : add `undefined` to return type of `.getOptionValueSource()` ([#1794])
+
+### Changed
+
+- additions to README
+
 ## [9.4.0] (2022-07-15)
 
 ### Added
@@ -1095,6 +1107,8 @@ program
 [#1756]: https://github.com/tj/commander.js/pull/1756
 [#1763]: https://github.com/tj/commander.js/pull/1763
 [#1767]: https://github.com/tj/commander.js/pull/1767
+[#1794]: https://github.com/tj/commander.js/pull/1794
+[#1795]: https://github.com/tj/commander.js/pull/1795
 
 <!-- Referenced in 5.x -->
 [#1]: https://github.com/tj/commander.js/issues/1
@@ -1173,6 +1187,7 @@ program
 [#1028]: https://github.com/tj/commander.js/pull/1028
 
 [Unreleased]: https://github.com/tj/commander.js/compare/master...develop
+[9.4.1]: https://github.com/tj/commander.js/compare/v9.4.0...v9.4.1
 [9.4.0]: https://github.com/tj/commander.js/compare/v9.3.0...v9.4.0
 [9.3.0]: https://github.com/tj/commander.js/compare/v9.2.0...v9.3.0
 [9.2.0]: https://github.com/tj/commander.js/compare/v9.1.0...v9.2.0

Readme.md

@@ -1011,7 +1011,15 @@ program
 
 ### TypeScript
 
-If you use `ts-node` and  stand-alone executable subcommands written as `.ts` files, you need to call your program through node to get the subcommands called correctly. e.g.
+extra-typings: There is an optional project to infer extra type information from the option and argument definitions.
+This adds strong typing to the options returned by `.opts()` and the parameters to `.action()`.
+See [commander-js/extra-typings](https://github.com/commander-js/extra-typings) for more.
+
+```
+import { Command } from '@commander-js/extra-typings';
+```
+
+ts-node: If you use `ts-node` and  stand-alone executable subcommands written as `.ts` files, you need to call your program through node to get the subcommands called correctly. e.g.
 
 ```sh
 node -r ts-node/register pm.ts

lib/help.js

@@ -216,7 +216,7 @@ class Help {
 
   /**
    * Get the subcommand summary to show in the list of subcommands.
-   * (Fallback to description for backwards compatiblity.)
+   * (Fallback to description for backwards compatibility.)
    *
    * @param {Command} cmd
    * @returns {string}

package.json

@@ -1,6 +1,6 @@
 {
   "name": "commander",
-  "version": "9.4.0",
+  "version": "9.4.1",
   "description": "the complete solution for node.js command-line programs",
   "keywords": [
     "commander",

tests/deprecated.test.js

@@ -21,7 +21,7 @@ describe('option with regular expression instead of custom processing function',
     expect(program.opts().cheese).toEqual('tasty');
   });
 
-  test('when argument does mot matches regexp then value is default', () => {
+  test('when argument does not match regexp then value is default', () => {
     const program = new commander.Command();
     program
       .option('--cheese <type>', 'cheese type', /mild|tasty/, 'mild');