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

[Snyk] Upgrade chalk from 3.0.0 to 5.1.0 #226

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade chalk from 3.0.0 to 5.1.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 7 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2022-10-05.
Release notes
Package name: chalk
  • 5.1.0 - 2022-10-05

    v5.0.1...v5.1.0

  • 5.0.1 - 2022-03-08
    • Add main field to package.json for backwards compatibility with some developer tools 85f7e96

    v5.0.0...v5.0.1

  • 5.0.0 - 2021-11-26

    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.InstanceChalk
      • chalk.supportsColorsupportsColor
      • chalk.stderrchalkStderr
      • chalk.stderr.supportsColorsupportsColorStderr
    • 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

    v4.1.0...v5.0.0

  • 4.1.2 - 2021-07-30
    • Readme updates
  • 4.1.1 - 2021-04-21
  • 4.1.0 - 2020-06-09
    • Support template literals for nested calls (#392) 09ddbad

    v4.0.0...v4.1.0

  • 4.0.0 - 2020-04-02

    Breaking

    • Require Node.js 10 61999a4
    • Change the Level TypeScript type to be a union instead of enum f0f4638
    -if (chalk.level > Level.None) {}
    +if (chalk.level > 0) {}

    Improvements

    • Use Object.setPrototypeOf as __proto__ could potentially be disabled (#387) 63469d3

    v3.0.0...v4.0.0

  • 3.0.0 - 2019-11-09
    Read more
from chalk GitHub release notes
Commit messages
Package name: chalk
  • 92c55db 5.1.0
  • d7d7571 Expose style names (#566)
  • 96f44c9 Meta tweaks
  • c231162 Use template literal types for simple color name transformations in the TypeScript types (#564)
  • ba5c385 Update screenshot
  • 503b9d3 Update Replit badge (#551)
  • b17d862 Improve browser detection (#542)
  • d28690e Refactor: Replace deprecated `String#substr()` (#541)
  • bccde97 5.0.1
  • 85f7e96 Add `main` field to package.json for backwards compatibiltiy
  • 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
  • 48d25d1 Meta tweaks
  • b68c8b5 Meta tweaks
  • f8a3642 Minor tweaks (#437)
  • 4cf2e40 Add `overline` style and remove `keyword`, `hsl`, `hsv`, `hwb` and `ansi` color spaces (#433)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants