Update dependency cosmiconfig to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cosmiconfig	^7.0.0 -> ^8.3.6

---

Release Notes

cosmiconfig/cosmiconfig (cosmiconfig)

v8.3.6

Compare Source

Bug Fixes

• ignore search place if accessing it causes ENOTDIR (i.e. if access of a subpath of a file is attempted) (5bd915a)

v8.3.5

Compare Source

Bug Fixes

• pass null to transform function for backwards compat (2b38510)

v8.3.4

Compare Source

Bug Fixes

• remove node: prefix from imports (f76484a), closes #​323

v8.3.3

Compare Source

Bug Fixes

• add back node 14 compat (7392541), closes #​320

v8.3.2

Compare Source

Bug Fixes

• use .cjs extension for sync compiled typescript (0d76a9a)
• use default for async TS loader (5bed3e3)

v8.3.1

Compare Source

Bug Fixes

• do not resolve stopDir when undefined (59082e2), closes #​317

v8.3.0

Compare Source

Features

• add support for TypeScript configuration files (d88b1b4)
• add support for TypeScript configuration files (d88b1b4)
• add support for TypeScript configuration files (a9c7ada)

v8.2.0

Compare Source

• Add support for ECMAScript modules (ESM) to the asynchronous API. End users running Node versions that support ESM can provide .mjs files, or .js files whose nearest parent package.json file contains "type": "module".
  • ${moduleName}rc.mjs and ${moduleName}.config.mjs are included in the default searchPlaces of the asynchronous API.
  • The synchronous API does not support ECMAScript modules, so does not look for .mjs files.
  • To learn more, read "Loading JS modules".

v8.1.3

Compare Source

• Fixed: existence of meta config breaking default loaders

v8.1.2

Compare Source

• Fixed: generation of TypeScript types going to the wrong output path

v8.1.1

Compare Source

• Fixed: meta config overriding original options completely (now merges correctly)

v8.1.0

Compare Source

• Added: always look at .config.{yml,yaml,json,js,cjs} file to configure cosmiconfig itself, and look for tool configuration in it using packageProp (similar to package.json)
  • For more info on this, look at the end user configuration section of the README

v8.0.0

Compare Source

No major breaking changes! We dropped support for Node 10 and 12 -- which you're probably not using. And we swapped out the YAML parser -- which you probably won't notice.

• Breaking change: Drop support for Node 10 and 12.

• Breaking change: Use npm package js-yaml to parse YAML instead of npm package yaml.

• Added: Loader errors now include the path of the file that was tried to be loaded.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Post-upgrade command 'npx beachball@latest change --no-fetch --no-commit --type patch --message '{{{commitMessage}}}'' has not been added to the allowed list in allowedPostUpgradeCommands

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.