Add support to `.cjs` (common) and `.mjs` (module) config file

Expected Behavior

If config file is commitlint.config.mjs or commitlint.config.cjs is expected that works

Current Behavior

Is ignored

Affected packages

• load

Possible Solution

in commitlint/@commitlint/load/src/utils/load-config.ts at loadConfig:

// ...
	const moduleName = 'commitlint';
	const explorer = cosmiconfig(moduleName, {
		searchPlaces: [
			'package.json',
			`.${moduleName}rc`,
			`.${moduleName}rc.json`,
			`.${moduleName}rc.yaml`,
			`.${moduleName}rc.yml`,
			`.${moduleName}rc.ts`,
			`.${moduleName}rc.js`,
			`${moduleName}.config.ts`,
			`${moduleName}.config.js`,
                       // add it here
                       	`${moduleName}.config.cjs`,
			`${moduleName}.config.mjs`,
		],
		loaders: {
			'.ts': TypeScriptLoader,
		},
	};
// ...
```

[cherryblossom000]

v13.2.0 was technically a breaking change — in v13.1.0 (before #2698), commitlint.config.cjs worked as a config file without having to specify -g commitlint.config.cjs. Like @k2snowman69, I had to debug and look at the code to discover that commitlint.config.cjs is no longer being searched for.

It was quite confusing for me who just ran pnpm recursive upgrade and got this:

⧗   input: chore: upgrade deps
✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fhHij
    - Example config: https://git.io/fhHip [empty-rules]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

[songhn233]

v13.2.0 was technically a breaking change — in v13.1.0 (before #2698), commitlint.config.cjs worked as a config file without having to specify -g commitlint.config.cjs. Like @k2snowman69, I had to debug and look at the code to discover that commitlint.config.cjs is no longer being searched for.

It was my mistake. In the pr at the time we discussed about the support of cjs.

My opinion is that cosmiconfig currently does not support esm. The distinction between cjs and mjs will only be necessary in the future when mjs is supported by default.

However, in fact when "type": "module" is declared in package.json, it is necessary to use cjs in order to support module.export syntax, and there is also a default configuration for cjs before, which will cause potential breaking changes if modified.

In case this happens in the future, for example, cosmiconfig supports mjs but now the searchplace overwrites the default configuration, this should merge .ts or other formats to the default, but now cosmiconfig does not export the default searchplace. So it may be difficult to sync.