chalk breaking changes
Every breaking API change we have recorded in chalk on npm: 7 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change July 26, 2026
On this page
6.0.0
- Removed
Node.js versions below 22 are no longer supported, so upgrade Node.js to 22 or later before using this release. github.com - Configuration changed
A numeric FORCE_COLOR value now sets an exact color level instead of the previous behavior, so check any FORCE_COLOR settings that use numbers. github.com - Signature changed
backgroundColors
Was const backgroundColors: readonly BackgroundColor[]; now const backgroundColors: readonly BackgroundColorName[]. npmjs.com - Signature changed
colors
Was const colors: readonly Color[]; now const colors: readonly ColorName[]. npmjs.com - Signature changed
foregroundColors
Was const foregroundColors: readonly ForegroundColor[]; now const foregroundColors: readonly ForegroundColorName[]. npmjs.com - Signature changed
modifiers
Was const modifiers: readonly Modifiers[]; now const modifiers: readonly ModifierName[]. npmjs.com - Signature changed
Options.level
Was readonly level?: ColorSupportLevel; now readonly level?: ColorSupportLevel | undefined. npmjs.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp