fix(deps): update dependency chalk to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
chalk	4.1.2 -> 5.3.0

---

Release Notes

chalk/chalk (chalk)

v5.3.0

Compare Source

• Add sideEffects field to package.json 5aafc0a
• Add support for Gitea Actions (#​603) 29b8569

v5.2.0

Compare Source

• Improve Deno compatibility (#​579) 7443e9f
• Detect true-color support for GitHub Actions (#​579) 7443e9f
• Detect true-color support for Kitty terminal (#​579) 7443e9f
• Fix test for Azure DevOps environment (#​579) 7443e9f

v5.1.2

Compare Source

• Fix exported styles names (#​569) a34bcf6

v5.1.1

Compare Source

• Improved the names of exports introduced in 5.1.0 (#​567) 6e0df05
  • We of course preserved the old names.

v5.1.0

Compare Source

• Expose style names (#​566) d7d7571

v5.0.1

Compare Source

• Add main field to package.json for backwards compatibility with some developer tools 85f7e96

v5.0.0

Compare Source

Breaking

• This package is now pure ESM. Please read this.
  • If you use TypeScript, you need to use TypeScript 4.7 or later. Why.
  • If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
  • The Chalk issue tracker is not a support channel for your favorite build/bundler tool.
  • It's totally fine to stay on Chalk v4. It's been stable for years.
• Require Node.js 12.20 fa16f4e
• Move some properties off the default export to individual named exports:
  • chalk.Instance → Chalk
  • chalk.supportsColor → supportsColor
  • chalk.stderr → chalkStderr
  • chalk.stderr.supportsColor → supportsColorStderr
• Remove .keyword(), .hsl(), .hsv(), .hwb(), and .ansi() coloring methods (#​433) 4cf2e40
  • These were not commonly used and added a lot of bloat to Chalk. You can achieve the same by using the color-convert package.
• The tagged template literal support moved into a separate package: chalk-template (#​524) c987c61

-import chalk from 'chalk';
+import chalkTemplate from 'chalk-template';

-chalk`2 + 3 = {bold ${2 + 3}}`;
+chalkTemplate`2 + 3 = {bold ${2 + 3}}`;

Improvements

• Bundle dependencies 04fdbd6
  • This means Chalk no longer has any dependencies 🎉
• The install size is less than half of v4.
• Add overline style (#​433) 4cf2e40
• Preserve function prototype methods (#​434) 0fba91b

---

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 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: package-lock.json

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @fimbul/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/tslint
npm WARN   dev tslint@"6.1.3" from the root project
npm WARN   3 more (tslint-clean-code, tslint-no-circular-imports, tslint-plugin-prettier)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer tslint@"^5.0.0" from @fimbul/[email protected]
npm WARN node_modules/@fimbul/bifrost
npm WARN   @fimbul/bifrost@"^0.21.0" from [email protected]
npm WARN   node_modules/tslint-consistent-codestyle
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/tslint
npm WARN   peer tslint@"^5.0.0" from @fimbul/[email protected]
npm WARN   node_modules/@fimbul/bifrost
npm WARN     @fimbul/bifrost@"^0.21.0" from [email protected]
npm WARN     node_modules/tslint-consistent-codestyle
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/tslint
npm ERR!   dev tslint@"6.1.3" from the root project
npm ERR!   peer tslint@">=5.1.0" from [email protected]
npm ERR!   node_modules/tslint-clean-code
npm ERR!     dev tslint-clean-code@"0.2.10" from the root project
npm ERR!   2 more (tslint-no-circular-imports, tslint-plugin-prettier)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tslint@"^5.11.0" from [email protected]
npm ERR! node_modules/tslint-config-airbnb
npm ERR!   dev tslint-config-airbnb@"5.11.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/tslint
npm ERR!   peer tslint@"^5.11.0" from [email protected]
npm ERR!   node_modules/tslint-config-airbnb
npm ERR!     dev tslint-config-airbnb@"5.11.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/212ed5/089d4e/cache/others/npm/_logs/2023-07-22T03_54_11_238Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/212ed5/089d4e/cache/others/npm/_logs/2023-07-22T03_54_11_238Z-debug-0.log