Upgrade chalk: 4.1.0 → 5.2.0 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ chalk (4.1.0 → 5.2.0) · Repo

Release Notes

5.2.0

• 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...v5.2.0

5.1.2

• Fix exported styles names (#569) a34bcf6

v5.1.1...v5.1.2

5.1.1

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

v5.1.0...v5.1.1

5.1.0

• Expose style names (#566) d7d7571

v5.0.1...v5.1.0

5.0.1

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

v5.0.0...v5.0.1

5.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 🎉
• The install size is less than half of v4.
• Add overline style (#433) 4cf2e40
• Preserve function prototype methods (#434) 0fba91b

v4.1.0...v5.0.0

4.1.2

• Readme updates

4.1.1

• Readme updates 89e9e3a

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 49 commits:

• 5.2.0
• Update `supports-color` dependency (#579)
• Minor tweaks
• Update Replit badge (#576)
• Update link to Truecolor in the readme (#573)
• 5.1.2
• Fix exported styles names (#569)
• 5.1.1
• Export styles from `ansi-styles` (#567)
• 5.1.0
• Expose style names (#566)
• Meta tweaks
• Use template literal types for simple color name transformations in the TypeScript types (#564)
• Update screenshot
• Update Replit badge (#551)
• Improve browser detection (#542)
• Refactor: Replace deprecated `String#substr()` (#541)
• 5.0.1
• Add `main` field to package.json for backwards compatibiltiy
• 5.0.0
• Fix code coverage
• Bundle dependencies
• Upgrade dependencies
• Re-export types from `supports-color` (#526)
• Remove support for tagged template literals (#524)
• Update dependents number in readme (#521)
• Meta tweak (#520)
• Minor tweaks
• Add `types` field to package.json
• Meta tweaks
• Meta tweaks
• Minor tweaks (#437)
• Add `overline` style and remove `keyword`, `hsl`, `hsv`, `hwb` and `ansi` color spaces (#433)
• Keep function prototype methods (#434)
• Add named exports (#432)
• Require Node.js 12 and move to ESM
• Meta tweaks
• Meta tweaks
• Rename `master` branch to `main`
• Update badge
• Update a link
• Move to GitHub Actions (#426)
• Add @Qix- to funding.yml
• Add Dev badge
• Only iterate through models once (#421)
• remove fixed number of iterations (#406)
• Update test dependencies (#414)
• Add browser support information (#415)
• Update readme.md

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)