chore(deps): update dependency cosmiconfig to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
cosmiconfig	^8 -> ^10.0.0

---

Release Notes

cosmiconfig/cosmiconfig (cosmiconfig)

v10.0.0

Compare Source

• Breaking change: The required version range is now ^22.18 || >=24.
• Breaking change: Remove typescript in favor of Node's own type stripping. This means that TypeScript 7 projects are supported, but non-erasable type syntax like namespace or enum is unsupported.
• Breaking change: JSON parsing uses the JSON.parse function directly. parse-json is no longer used for better error messages, since Node has improved theirs.
• Remove import-fresh dependency in favor of directly clearing the cache.
• Added support for UTF-16 config files

v9.0.2

Compare Source

• Fixed a prototype chain issue that may happen when merging different config objects.
• Fixed the project search strategy not correctly stopping at the package boundary.

v9.0.1

Compare Source

• Fixed a race condition where multiple instances existing simultaneously could cause cosmiconfig to fail to load TypeScript config files.
• Fixed an issue on Windows where CWD being a short path (e.g. C:\Users\USERNA~1) would cause cosmiconfig to fail to load ESM config files.

v9.0.0

Compare Source

• Added searchStrategy option:
  • The none value means that cosmiconfig does not traverse any directories upwards.
    • Breaking change: This is the default value if you don't pass a stopDir option, which means that cosmiconfig no longer traverses directories by default, and instead just looks in the current working directory.
      • If you want to achieve maximum backwards compatibility without adding an explicit stopDir, add the searchStrategy: 'global' option.
  • The project value means that cosmiconfig traverses upwards until it finds a package.json (or .yaml) file.
  • The global value means that cosmiconfig traverses upwards until the passed stopDir, or your home directory if no stopDir is given.
• Breaking change: Meta config files (i.e. config.js and similar) are not looked for in the current working directory anymore. Instead, it looks in the .config subfolder.
• Breaking change: When defining searchPlaces in a meta config file, the tool-defined searchPlaces are merged into this. Users may specify mergeSearchPlaces: false to disable this.
• Added support for a special $import key which will import another configuration file
  • The imported file will act as a base file - all properties from that file will be applied to the configuration, but can be overridden by the importing file
  • For more information, read the import section of the README
• Added searching in OS conventional folders (XDG compatible on Linux, %APPDATA% on Windows, Library/Preferences on macOS) for searchStrategy: 'global'
• Fixed crash when trying to load a file that is not readable due to file system permissions
• Fixed wrong ERR_REQUIRE_ESM error being thrown when there is an issue loading an ESM file

---

Configuration

📅 Schedule: (UTC)

• 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 was generated by Mend Renovate. View the repository job log.

[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: deno.lock

Command failed: deno install --frozen=false
�[0m�[32mDownload�[0m https://registry.npmjs.org/@babel%2fcode-frame
�[0m�[32mDownload�[0m https://registry.npmjs.org/@babel%2fhelper-validator-identifier
�[0m�[32mDownload�[0m https://registry.npmjs.org/@babel%2fhighlight
�[0m�[32mDownload�[0m https://registry.npmjs.org/@faker-js%2ffaker
�[0m�[32mDownload�[0m https://registry.npmjs.org/@types%2fnode
�[0m�[32mDownload�[0m https://registry.npmjs.org/ansi-styles
�[0m�[32mDownload�[0m https://registry.npmjs.org/argparse
�[0m�[32mDownload�[0m https://registry.npmjs.org/callsites
�[0m�[32mDownload�[0m https://registry.npmjs.org/chalk
�[0m�[32mDownload�[0m https://registry.npmjs.org/color-convert
�[0m�[32mDownload�[0m https://registry.npmjs.org/color-name
�[0m�[32mDownload�[0m https://registry.npmjs.org/commander
�[0m�[32mDownload�[0m https://registry.npmjs.org/cosmiconfig
�[0m�[32mDownload�[0m https://registry.npmjs.org/error-ex
�[0m�[32mDownload�[0m https://registry.npmjs.org/escape-string-regexp
�[0m�[32mDownload�[0m https://registry.npmjs.org/has-flag
�[0m�[32mDownload�[0m https://registry.npmjs.org/import-fresh
�[0m�[32mDownload�[0m https://registry.npmjs.org/is-arrayish
�[0m�[32mDownload�[0m https://registry.npmjs.org/js-tokens
�[0m�[32mDownload�[0m https://registry.npmjs.org/js-yaml
�[0m�[32mDownload�[0m https://registry.npmjs.org/json-parse-even-better-errors
�[0m�[32mDownload�[0m https://registry.npmjs.org/lines-and-columns
�[0m�[32mDownload�[0m https://registry.npmjs.org/ms
�[0m�[32mDownload�[0m https://registry.npmjs.org/parent-module
�[0m�[32mDownload�[0m https://registry.npmjs.org/parse-json
�[0m�[32mDownload�[0m https://registry.npmjs.org/path-type
�[0m�[32mDownload�[0m https://registry.npmjs.org/playwright-core
�[0m�[32mDownload�[0m https://registry.npmjs.org/playwright
�[0m�[32mDownload�[0m https://registry.npmjs.org/radash
�[0m�[32mDownload�[0m https://registry.npmjs.org/resolve-from
�[0m�[32mDownload�[0m https://registry.npmjs.org/supports-color
�[0m�[1m�[31merror�[0m: Could not find npm package 'cosmiconfig' matching '^10.0.0'.

A newer matching version was found, but it was not used because it was newer than the specified minimum dependency date of 2026-08-01 19:31:29.717185124 UTC.

�[0m�[33mhint:�[0m This version is blocked by the minimum dependency age policy, which avoids installing recently published versions to reduce supply chain risk (the default is 24 hours). To use this version now, pass the �[0m�[1m--minimum-dependency-age�[0m (or �[0m�[1m--min-dep-age�[0m) flag (for example �[0m�[1m0�[0m to disable it, or a shorter duration like �[0m�[1m60�[0m minutes) or set �[0m�[1m"minimumDependencyAge"�[0m in your deno.json, or wait until the version is old enough.
�[0m�[33mdocs:�[0m �[0m�[36mhttps://docs.deno.com/go/minimum-dependency-age�[0m