Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade chalk to version 3.0.0 #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 10, 2019

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 (^2.4.2 → ^3.0.0) · Repo

Release Notes

3.0.0

This release has been in development for more than a year and massively improves performance and the time it takes to import Chalk.

Thanks to @stroncium for his hard work on this. 🙌

Breaking

  • Require Node.js 8 3ef170b
  • Remove the .enabled property in favor of .level (#356) 1f77953
    • Why: It was confusing to users to have two properties for detecting color support.
    • Migrate:
-if (chalk.enabled) {}
+if (chalk.level > 0) {}
  • Remove chalk.constructor() in favor of chalk.Instance() (#322) de2f4cd
    • Migrate:
-new chalk.constructor({level: 1});
+new chalk.Instance({level: 1})

Minor breaking

-import chalk from 'chalk';
+import chalk = require('chalk');
  • Drop built-in Flow type definition d3be9c6
    • Why: None of us use Flow and we were not good at maintaining the type definition. You can get the types at flow-typed (needs to be updated to Chalk v3, open an issue on flow-typed).
  • Rename the ChalkOptions TypeScript type to Options cf66156
  • Remove dim style workaround for Windows (#331) cd5de7a
    • Why: The issue was fixed in newer Windows 10 builds.
  • Remove the blue color workaround for Windows (#330) 2ca015c
    • Why: The issue was fixed in newer Windows 10 builds.

Enhancements

  • Massively improve performance! (#337) c08417e
  • Improve require speed (#358) 61aca7c
  • Add chalk.stderr for printing to stderr (#359) 2a53389
  • Add blackBright color. It's the same as the gray color, but added for consistency. c25c32a
  • Fix support for bracketed Unicode escapes in template literals (#350) 9830948
  • Export TypeScript types for colors and modifiers (#357) 6b4d206
  • Add ansi256 and bgAnsi256 to TypeScript declaration (#368) fb8e85a
  • Add ansi and bgAnsi to TypeScript declaration (#369) 18c280d

Color detection

Fixes

  • Fix support for nested styles (#335) 87156ce
  • Fix const enum for TypeScript (#364) 4e65299
  • Fix TypeScript type for supportsColor which is top‑level only (#342) b3e9b91
  • Fix TypeScript type for chalk.supportsColor (#347) d82b2a6
  • Fix TypeScript type for tagged template literal argument to accept unknown instead of just string (#316) 7f6e563

v2.4.1...v3.0.0

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


👉 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 Status

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 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)

@depfu depfu bot added the depfu label Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants