Bump chalk from 4.1.2 to 5.0.0

[dependabot]

Bumps chalk from 4.1.2 to 5.0.0.

Release notes

Sourced from chalk's releases.

v5.0.0

Breaking

• This package is now pure ESM. Please read this.
  • If you use TypeScript, you will want to stay on Chalk 4 until TypeScript 4.6 is out. 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.
• 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';
-chalk2 + 3 = {bold ${2 + 3}};
+chalkTemplate2 + 3 = {bold ${2 + 3}};

Improvements

• Bundle dependencies 04fdbd6
  • This means Chalk no longer has any dependencies 🎉
• Add overline style (#433) 4cf2e40
• Preserve function prototype methods (#434) 0fba91b

chalk/chalk@v4.1.0...v5.0.0

Commits

• 4d5c479 5.0.0
• 7a68935 Fix code coverage
• 04fdbd6 Bundle dependencies
• d7c4aac Upgrade dependencies
• 09fd5c4 Re-export types from supports-color (#526)
• c987c61 Remove support for tagged template literals (#524)
• f478655 Update dependents number in readme (#521)
• 3761e45 Meta tweak (#520)
• 9521742 Minor tweaks
• 625a285 Add types field to package.json
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Dear dependabot[bot]

Thank you for contributing to the JavaScript track on Exercism! 💙
You will see some automated feedback below 🤖. It would be great if you can make sure your PR covers those points. This will save your reviewer some time and your change can be merged quicker.

• ✍️ If your PR is not related to an existing issue (and is not self-explaining like a typo fix), please make sure the description explains why the change you made is necessary.

• 🔤 If your PR fixes an easy to identify typo, if would be great if you could check for that typo in the whole repo. For example, if you found Unicdoe, use "replace all" in your editor (or command line magic) to fix it consistently.

Dear Reviewer/Maintainer

• 📏 Make sure you set the appropriate x:size label for the PR. (This also works after merging, in case you forgot about it.)

• 🔍 Don't be too nit-picky. If the PR is a clear improvement compared to the status quo, it should be approved as clear signal this is good to be merged even if the minor comments you might have are not addressed by the contributor. Further improvement ideas can be captured in issues (if important enough) and implemented via additional PRs.

• 🤔 After reviewing the diff in the "Files changed" section, take a moment to think about whether there are changes missing from the diff. Does something need to be adjusted in other places so the code or content stays consistent?

_{Automated comment created by PR Commenter 🤖.}