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 2.4.2 to 5.0.1 #3

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

Conversation

mikolajroszak
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade chalk from 2.4.2 to 5.0.1.

ℹ️ 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 9 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2022-03-08.
Release notes
Package name: chalk
  • 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 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.
      • 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
  • 3.0.0-beta.2 - 2019-10-08

    While this is a beta release, the code is well-tested and fairly stable.
    We encourage you to test it out and report any issues.

    $ npm install [email protected]
    

    See the beta 1 release notes for more.


    • Add ansi256 and bgAnsi256 to TypeScript declarations (#368) fb8e85a

    v3.0.0-beta.1...v3.0.0-beta.2

  • 3.0.0-beta.1 - 2019-09-27
    Read more
  • 2.4.2 - 2019-01-05

    This release is done from the v2-release branch, as master branch targets the work-in-progress v3 release.

from chalk GitHub release notes
Commit messages
Package name: chalk

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants