{"ecosystem":"npm","package":"chalk","version":null,"bugs":[{"id":151,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:41","title":"`reset` order inconsistency","description":"This outputs in yellow:\n\n``` js\nconsole.log(chalk.yellow.reset('unicorn'));\n```\n\nThis without a style:\n\n``` js\nconsole.log(chalk.reset.yellow('unicorn'));\n```\n\nOur docs say the styles aren't order dependent, but with reset they clearly are.\n\n@jbnicolai thoughts on how this should be handled?\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/41","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.033449+00:00","updated_at":"2026-04-19T04:30:31.033449+00:00"},{"id":150,"ecosystem":"npm","package_name":"chalk","affected_version":"2.0.0","fixed_version":null,"bug_id":"github:164","title":"AppVeyor (Windows) throws `Cannot read property 'toLowerCase' of undefined`","description":"Via a chalk 2.0.0 pull request I'm seeing ~300 instances of the following error for stylelint on our Windows AppVeyor builds:\r\n\r\n```shell\r\n FAIL lib\\rules\\selector-max-empty-lines\\__tests__\\index.js\r\n ● Test suite failed to run\r\n TypeError: Cannot read property 'toLowerCase' of undefined\r\n \r\n at Object. (node_modules/chalk/index.js:8:78)\r\n at Object. (lib/formatters/stringFormatter.js:5:15)\r\n at Object. (lib/formatters/index.js:5:11)\r\n FAIL lib\\rules\\selector-no-qualifying-type\\__tests__\\index.js\r\n```\r\n\r\n• chalk ref: https://github.com/chalk/chalk/blob/master/index.js#L8\r\n• stylelint AppVeyor build: https://ci.appveyor.com/project/stylelint/stylelint/build/4476\r\n• stylelint pull request / issue: https://github.com/stylelint/stylelint/pull/2695\r\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/164","labels":["bug"],"created_at":"2026-04-19T04:30:31.032837+00:00","updated_at":"2026-04-19T04:30:31.032837+00:00"},{"id":149,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:175","title":"Truecolor methods crash when color is unsupported","description":"When `supports-color` returns `false`, `supportsColor.level` equals `undefined` here: https://github.com/chalk/chalk/blob/master/index.js#L22. This makes `this.level` equal `undefined` here https://github.com/chalk/chalk/blob/master/index.js#L75 and as a result, crashes when color is unsupported. This can be reproduced by executing a script with chalk output using `child_process.spawn()` and piping output to stdout.\r\n\r\nThe fix is to change this:\r\n\r\n```js\r\nobj.level = options.level === undefined ? supportsColor.level : options.level;\r\n```\r\n\r\nto this:\r\n\r\n```js\r\nobj.level = options.level === undefined ? (supportsColor.level || 0) : options.level;\r\n```\r\n\r\nI stumbled upon this issue when tests were passing in terminal and on Travis CI, but were failing when run by `np`.\r\n\r\nI submitted a PR with a failing test here https://github.com/chalk/chalk/pull/174. If I didn't miss anything, I will modify this PR to fix the problem.\r\n\r\nNote, that \"regular\" (e.g. `chalk.blue()`) methods don't fail.","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/175","labels":["bug"],"created_at":"2026-04-19T04:30:31.032345+00:00","updated_at":"2026-04-19T04:30:31.032345+00:00"},{"id":148,"ecosystem":"npm","package_name":"chalk","affected_version":"8.1.2","fixed_version":null,"bug_id":"github:176","title":"Got a error when use `chalk.bgHex()` with arg `--no-color`","description":"```js\r\nconst chalk = require('chalk');\r\ntry {\r\n\tchalk.bgHex('#cccccc')('message');\r\n} catch (ex) {\r\n\tconsole.error(ex);\r\n}\r\n```\r\n```bash\r\nE:\\work\\gulp-reporter (master) (gulp-reporter@2.1.0)\r\n$ node -v\r\nv8.1.2\r\n\r\nE:\\work\\gulp-reporter (master) (gulp-reporter@2.1.0)\r\n$ node test.js --no-color\r\nTypeError: Cannot read property 'hex' of undefined\r\n at Function. (E:\\work\\gulp-reporter\\node_modules\\chalk\\index.js:98:57)\r\n at errors.map (E:\\work\\gulp-reporter\\lib\\formater.js:240:19)\r\n at Array.map (native)\r\n at formater (E:\\work\\gulp-reporter\\lib\\formater.js:235:18)\r\n at reporter (E:\\work\\gulp-reporter\\lib\\reporter.js:20:10)\r\n at getErrors.then.errors (E:\\work\\gulp-reporter\\lib\\gulp-plugin.js:19:19)\r\n\r\n```","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/176","labels":["bug"],"created_at":"2026-04-19T04:30:31.031833+00:00","updated_at":"2026-04-19T04:30:31.031833+00:00"},{"id":147,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:177","title":"Newline character (\\n) in tagged template literals becomes \"n\"","description":"From the comment here: https://github.com/chalk/chalk/issues/12#issuecomment-315685346\r\n> When using tagged template literals, `\\n` does not work => `n` is output and there is no line break.\r\n\r\nI just ran into this myself, so I figured I'd do as @Qix- asked.\r\n\r\n------\r\n\r\nIt looks like part of your processing is eating the `\\`. Multi-line template literals (or anything similar in other languages) always seem like a cool idea until you have code like this...\r\n\r\n```js\r\nfunction run() {\r\n\tif (something) {\r\n\t\tif (somethingElse) {\r\n\t\t\tconsole.log(`this is the first line\r\n\t\t\tthis is the second`);\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n...producing the output...\r\n\r\n```\r\nthis is the first line\r\n\t\t\tthis is the second\r\n```\r\n\r\n...which isn't optimal. You could pull the second line all the way to the margin, but that'd never fly with formatters or linters.\r\n\r\nMaybe there's a better way for chalk to detect character escapes (certain character escapes) and not eat them?\r\n\r\nAs a workaround, it is possible to do something like this, though it's not very attractive:\r\n\r\n```js\r\nconsole.log(chalk`{red NO} but...${'\\n'}really, {green YES}`);\r\n```","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/177","labels":["bug"],"created_at":"2026-04-19T04:30:31.031379+00:00","updated_at":"2026-04-19T04:30:31.031379+00:00"},{"id":146,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:184","title":"The {} placeholder removes the linebreak that's just before it","description":"In a multiline chalk template string, the {} placeholder removes the linebreak that's just before it (i.e. if it is at the beginning of any line).\r\n\r\nSo for example:\r\n``` \r\nchalk`The first line\r\n{red The second line in red}`\r\n```\r\nproduces:\r\n```\r\nThe first lineThe second line in red\r\n```\r\nwhen it should produce:\r\n```\r\nThe first line\r\nThe second line in red\r\n```\r\n\r\nThis bug does not happen if the {} placeholder is located anywhere after the beginning of a line.\r\n\r\nI don't know if this is related to #177 or #12 but at first glance this seems like a distinct bug to me.","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/184","labels":["bug"],"created_at":"2026-04-19T04:30:31.030891+00:00","updated_at":"2026-04-19T04:30:31.030891+00:00"},{"id":145,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:187","title":"Root chalk function doesn't support multiple arguments if used in template mode","description":"When creating a chalk object with template functionality:\r\n\r\n```javascript\r\nconst ctx = chalk.constructor({level: 0}); // no new; templates enabled\r\n```\r\ncalling a style with multiple arguments will concatenate them with spaces\r\n\r\n```javascript\r\nconst str = ctx.red('hello', 'there'); //-> \"hello there\"\r\n```\r\n\r\nbut calling the root function doesn't:\r\n\r\n```javascript\r\nconst str = ctx('hello', 'there'); // -> \"hello\"\r\n```","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/187","labels":["bug"],"created_at":"2026-04-19T04:30:31.030453+00:00","updated_at":"2026-04-19T04:30:31.030453+00:00"},{"id":144,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:189","title":"Should we match console.log(fmt, ...) formatting with chalk?","description":"Right now, we do a simple `.join(' ')` on arguments. While this covers most cases, this isn't 100% analogous to `console.xxx()` functions.\r\n\r\nUnder the hood, the `console.xxx()` functions use [`util.format()`](https://nodejs.org/api/util.html#util_util_format_format_args).\r\n\r\nShould we be using it?\r\n\r\n// cc @sindresorhus ","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/189","labels":["bug","question"],"created_at":"2026-04-19T04:30:31.030002+00:00","updated_at":"2026-04-19T04:30:31.030002+00:00"},{"id":143,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:194","title":"Interpolated template expressions that evaluate to `undefined` or `null` throw exception","description":"Getting the following error message with template literals:\r\n\r\n```\r\n> chalk`hello ${undefined}`\r\n\r\nTypeError: Cannot read property 'toString' of undefined\r\n at chalkTag (/src/bitlang/bootstrap/node_modules/chalk/index.js:210:25)\r\n at Chalk.chalk.template (/src/bitlang/bootstrap/node_modules/chalk/index.js:36:20)\r\n```","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/194","labels":["bug"],"created_at":"2026-04-19T04:30:31.029560+00:00","updated_at":"2026-04-19T04:30:31.029560+00:00"},{"id":142,"ecosystem":"npm","package_name":"chalk","affected_version":"2.3.0","fixed_version":null,"bug_id":"github:234","title":"chalk.enabled=true or { enabled: true} does not work when color support is initially detected as false","description":"\n[\"Issuehunt](https://issuehunt.io/r/chalk/chalk/issues/234)\n\n\n\n## Environment\r\n**Chalk:** 2.3.0\r\n**Node.js:** 6.12.0 and 8.9.3\r\n\r\n## Issue\r\n**chalk.js** \r\n```js\r\nconst chalk = require('chalk');\r\nchalk.enabled = true;\r\nconsole.log(chalk`{green hello}`);\r\n```\r\n--or--\r\n```js\r\nconst chalk = new require('chalk').constructor({ enabled: true });\r\n```\r\n\r\nIf you run **chalk.js** as:\r\n\r\n```\r\nnode chalk.js\r\n```\r\n\r\nThe output is a green `hello`.\r\n\r\nIf you run this in a clean environment (which causes **supports-color** to report that colors are not supported):\r\n\r\n```\r\nenv -i node chalk.js\r\n```\r\n\r\nThe output is a un-colored `hello`.\r\n\r\n## Details\r\nI traced this to https://github.com/chalk/chalk/blob/master/index.js#L177, where `this.enabled` is `false`, and `this` is `builder`. It seems like, somehow, the initial value for `enabled` is not getting changed or is not filtering down to the `enabled` property defined on `builder`.\r\n\r\nAs expected, using the environment variable `FORCE_COLOR` or the `--color` parameter does work, as it gets `enabled` to the right value, initially.\r\n\r\nInterestingly, running it as (to force it on from the start):\r\n\r\n```\r\nenv -i node chalk.js --color\r\n```\r\n...and then doing:\r\n```js\r\nchalk.enabled = false;\r\n```\r\n..._does_ actually turn it off. Now I'm thinking there's some issue with truthy and falsy. I'm not sure.\r\n\r\n## Aside\r\nIt would definitely be easier for me to dig more on this if there weren't _so much_ indirection in the way this is implemented :innocent:; but, I'm sure some or most of that is necessary to get this to work so cleanly.\n\n\n\n\n---\n\n
\n\nIssueHunt Summary\n\n\n#### [qix- qix-](https://issuehunt.io/u/qix-) has been rewarded.\n\n### Backers (Total: $40.00)\n\n- [issuehunt issuehunt](https://issuehunt.io/u/issuehunt) ($40.00)\n### Submitted pull Requests\n- [#356 Remove the `.enabled` property in favor of `.level`](https://issuehunt.io/r/chalk/chalk/pull/356)\n---\n\n### Tips\n\n- Checkout the [Issuehunt explorer](https://issuehunt.io/r/chalk/chalk/) to discover more funded issues.\n- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.\n---\nIssueHunt has been backed by the following sponsors. [Become a sponsor](https://issuehunt.io/membership/members)\n
\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/234","labels":["bug","help wanted",":gift: Rewarded on Issuehunt"],"created_at":"2026-04-19T04:30:31.029071+00:00","updated_at":"2026-04-19T04:30:31.029071+00:00"},{"id":141,"ecosystem":"npm","package_name":"chalk","affected_version":"2.3.0","fixed_version":null,"bug_id":"github:248","title":"Cannot read property 'hex' of undefined (only with v2.3.0)","description":"Hi,\r\n\r\nI use `chalk` to add colors to console logs in a personal project ([create-cozy-app](https://github.com/CPatchane/create-cozy-app)) and thanks a lot for your great job on this module 👍 \r\n\r\nBut something seems broken since the version 2.3.0. I use almost only the `chalk.hex()` method and I got this issue:\r\n\r\n```\r\nmyapptest/node_modules/cozy-scripts/node_modules/chalk/index.js:82\r\n\t\t\t\tconst open = ansiStyles.color[levelMapping[level]][model].apply(null, arguments);\r\n\t\t\t\t ^\r\n\r\nTypeError: Cannot read property 'hex' of undefined\r\n at Function. (myapptest/node_modules/cozy-scripts/node_modules/chalk/index.js:82:55)\r\n at Object. (myapptest/node_modules/cozy-scripts/utils/_colorize.js:7:15)\r\n at Module._compile (module.js:643:30)\r\n at Object.Module._extensions..js (module.js:654:10)\r\n at Module.load (module.js:556:32)\r\n at tryModuleLoad (module.js:499:12)\r\n at Function.Module._load (module.js:491:3)\r\n at Module.require (module.js:587:17)\r\n at require (internal/module.js:11:18)\r\n```\r\n\r\nAll work well with the version 2.2.2 but also if I only use default colors (`chalk.blue()`, `chalk.bgWhite()`). And it seems to concern only my webpack usage like [here](https://github.com/CPatchane/create-cozy-app/blob/master/packages/cozy-scripts/config/webpack.config.progress.js#L16) or [here](https://github.com/CPatchane/create-cozy-app/blob/master/packages/cozy-scripts/scripts/watch.js#L20).\r\nI suppose that came from this commit so: https://github.com/chalk/chalk/commit/7be154c074026f77b99e7d854b3a4cdd5e4ae502\r\n\r\nHope that will help.","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/248","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.028543+00:00","updated_at":"2026-04-19T04:30:31.028543+00:00"},{"id":140,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:254","title":"Chalk doesn't detect color support for VSCode Debug Console","description":"Chalk works perfect for nearly all use cases we have and we make heavy use of testing for `chalk.enabled` to decide how we format our log output. This works in the local command line as expected and logs are printed colorfully.\r\n\r\nSince we're switching from Atom to VSCode I've noticed that the color mode detection doesn't seem to work for the VSCode console. `chalk` reports `supportsColor` and `enabled` both being false. The VSCode Debug Console clearly supports colors and if I manually enforce `chalk` to use colors it works fine and as expected. But I wonder if this automatic detection is something that can be fixed? \r\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/254","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.027858+00:00","updated_at":"2026-04-19T04:30:31.027858+00:00"},{"id":139,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:257","title":"Add \"bright black\" and use \"gray\" as alias","description":"For consistency, it would be good to have a `chalk.blackBright` for use.\r\n\r\nSimilarly, it'd be nice if there was a \"background\" color alias for gray: `chalk.bgGray`.","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/257","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.027370+00:00","updated_at":"2026-04-19T04:30:31.027370+00:00"},{"id":138,"ecosystem":"npm","package_name":"chalk","affected_version":"2.3.2","fixed_version":null,"bug_id":"github:271","title":"Destructuring `hex` not working","description":"**Bug reporting**\r\n\r\nIt's not possible to destructure `hex` function.\r\n\r\n**My code**\r\n\r\n*Chalk version*: 2.3.2\r\n*Node version*: 9.4\r\n\r\n```js\r\nconst {hex} = require('chalk');\r\nhex('#013370')('strapi');\r\n```\r\n\r\n**Error output**\r\n\r\n```shell\r\nTypeError: Cannot read property '_styles' of undefined\r\nat ./node_modules/chalk/index.js:88:34\r\n```","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/271","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.026920+00:00","updated_at":"2026-04-19T04:30:31.026920+00:00"},{"id":137,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:290","title":"Nested `.dim()` affects surrounding styles too","description":"It seems `dim` doesn't handle being nested inside another style:\r\n\r\nThe following:\r\n\r\n```js\r\nconst chalk = require('chalk');\r\n\r\nconsole.log(chalk.bold(chalk.dim('bold-dim'), 'bold'));\r\n```\r\n\r\nProduces:\r\n\r\n\"screen\r\n\r\nWhile it should produce:\r\n\r\n\"screen\r\n\r\nI reproduced this in both Terminal.app and iTerm.app on macOS 10.13.\r\n\r\n// @Qix- Any ideas?","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/290","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.026472+00:00","updated_at":"2026-04-19T04:30:31.026472+00:00"},{"id":136,"ecosystem":"npm","package_name":"chalk","affected_version":"10.13.0","fixed_version":null,"bug_id":"github:325","title":"Bold resets previous color","description":"Depending on order and type of operations, `bold` causes a previously set color to be suppressed:\r\n\r\n![image](https://user-images.githubusercontent.com/361662/52567161-e8fe2b00-2e0b-11e9-8fc8-ffc04cf235b0.png)\r\n\r\n```\r\nchalk.bold(\"foo\") => '\\u001b[1mfoo\\u001b[22m'\r\nchalk.blue.bold(\"foo\") => '\\u001b[94m\\u001b[1mfoo\\u001b[22m\\u001b[39m'\r\nchalk.bold.blue(\"foo\") => '\\u001b[1m\\u001b[94mfoo\\u001b[39m\\u001b[22m'\r\nchalk.bold.hex(\"#0000ff\")(\"foo\") => '\\u001b[1m\\u001b[38;2;0;0;255mfoo\\u001b[39m\\u001b[22m'\r\nchalk.hex(\"#0000ff\").bold(\"foo\") => '\\u001b[38;2;0;0;255m\\u001b[1mfoo\\u001b[22m\\u001b[39m'\r\n```\r\n\r\nThe screenshot above was taken on Windows 10 1709 (Enterprise) using Node v10.13.0 through winpty 0.4.3 in mintty 2.8.1 installed with Git for Windows. Running node via Powershell or `cmd` yields identical ANSI sequences and similar results, as far as the coloration of the last sample is concerned, e.g.:\r\n\r\n![image](https://user-images.githubusercontent.com/361662/52568111-2663b800-2e0e-11e9-928f-2bb0bbf47fc3.png)\r\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/325","labels":["bug","question"],"created_at":"2026-04-19T04:30:31.025995+00:00","updated_at":"2026-04-19T04:30:31.025995+00:00"},{"id":135,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:334","title":"Nesting bug","description":"\n[\"Issuehunt](https://issuehunt.io/r/chalk/chalk/issues/334)\n\n\n\nIf the bug mention in https://github.com/doowb/ansi-colors#nested-styling-bug is valid, we should fix it.\n\n\n\n\n---\n\n
\n\nIssueHunt Summary\n\n\n#### [farnabaz farnabaz](https://issuehunt.io/u/farnabaz) has been rewarded.\n\n### Backers (Total: $80.00)\n\n- [issuehunt issuehunt](https://issuehunt.io/u/issuehunt) ($80.00)\n### Submitted pull Requests\n- [#335 fix(nested-styling): reopen closed style](https://issuehunt.io/r/chalk/chalk/pull/335)\n---\n\n### Tips\n\n- Checkout the [Issuehunt explorer](https://issuehunt.io/r/chalk/chalk/) to discover more funded issues.\n- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.\n---\nIssueHunt has been backed by the following sponsors. [Become a sponsor](https://issuehunt.io/membership/members)\n
\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/334","labels":["bug","help wanted",":gift: Rewarded on Issuehunt"],"created_at":"2026-04-19T04:30:31.025523+00:00","updated_at":"2026-04-19T04:30:31.025523+00:00"},{"id":134,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:338","title":"number to string casting (typescript: not assignable)","description":"```typescript\r\n// PLS do number to string casting automatically\r\nconsole.log(chalk`{yellowBright ${i.toString()} tries}`)\r\n```\r\nATM it throws a not assignable error when using without .toString()","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/338","labels":["bug","help wanted"],"created_at":"2026-04-19T04:30:31.025007+00:00","updated_at":"2026-04-19T04:30:31.025007+00:00"},{"id":133,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:341","title":"Template literals are unsupported for nested calls","description":"\n[\"Issuehunt](https://issuehunt.io/r/chalk/chalk/issues/341)\n\n\n\nThe following is unsupported despite it being allowed by the type system:\r\n```ts\r\nchalk.bold`Hello, {cyan.inverse ${name}!} This is a test. {green ${exclamation}!}`;\r\n```\r\nProduces:\r\n```\r\nHello, {cyan.inverse ,!} This is a test. {green ,!} Sindre Neat\r\n```\r\nInstead of:\r\n```\r\nHello, Sindre! This is a test. Neat!\r\n```\n\n\n\n\n---\n\n
\n\nIssueHunt Summary\n\n\n#### [toonijn toonijn](https://issuehunt.io/u/toonijn) has been rewarded.\n\n### Backers (Total: $40.00)\n\n- [issuehunt issuehunt](https://issuehunt.io/u/issuehunt) ($40.00)\n\n### Submitted pull Requests\n- [#392 Support for template literals for nested calls](https://issuehunt.io/r/chalk/chalk/pull/392)\n- [#398 Support nested calls](https://issuehunt.io/r/chalk/chalk/pull/398)\n---\n\n### Tips\n\n- Checkout the [Issuehunt explorer](https://issuehunt.io/r/chalk/chalk/) to discover more funded issues.\n- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.\n
\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/341","labels":["bug","help wanted",":gift: Rewarded on Issuehunt"],"created_at":"2026-04-19T04:30:31.024505+00:00","updated_at":"2026-04-19T04:30:31.024505+00:00"},{"id":132,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"github:349","title":"Bug: bracketed Unicode escapes not supported","description":"\n[\"Issuehunt](https://issuehunt.io/r/chalk/chalk/issues/349)\n\n\n\nRepro:\r\n\r\n```js\r\n// example.js\r\nconst chalk = require('chalk')\r\n\r\nconsole.log(chalk`\\u{2192} Running test {bold foo}...`)\r\n```\r\n\r\nExpected output:\r\n
→ Running test foo...
\r\n\r\nActual output:\r\n```\r\nError: Found extraneous } in Chalk template literal\r\n at node_modules/chalk/templates.js:109:11\r\n at String.replace ()\r\n at module.exports (node_modules/chalk/templates.js:99:6)\r\n at chalkTag (node_modules/chalk/index.js:221:9)\r\n at Chalk.chalk.template (node_modules/chalk/index.js:36:20)\r\n at Object. (example.js:3:17)\r\n```\n\n\n\n\n---\n\n
\n\nIssueHunt Summary\n\n\n#### [qix- qix-](https://issuehunt.io/u/qix-) has been rewarded.\n\n### Backers (Total: $50.00)\n\n- [issuehunt issuehunt](https://issuehunt.io/u/issuehunt) ($50.00)\n### Submitted pull Requests\n- [#350 Fix bracketed unicode escapes in template literals](https://issuehunt.io/r/chalk/chalk/pull/350)\n---\n\n### Tips\n\n- Checkout the [Issuehunt explorer](https://issuehunt.io/r/chalk/chalk/) to discover more funded issues.\n- Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds.\n---\nIssueHunt has been backed by the following sponsors. [Become a sponsor](https://issuehunt.io/membership/members)\n
\n","severity":"medium","status":"fixed","source":"github_issues","source_url":"https://github.com/chalk/chalk/issues/349","labels":["bug","help wanted",":gift: Rewarded on Issuehunt"],"created_at":"2026-04-19T04:30:31.023534+00:00","updated_at":"2026-04-19T04:30:31.023534+00:00"},{"id":131,"ecosystem":"npm","package_name":"chalk","affected_version":null,"fixed_version":null,"bug_id":"osv:MAL-2025-46969","title":"Malicious code in chalk (npm)","description":"The package was compromised and malicious code added.\n\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: ghsa-malware (985b6546ed08c8482326a4819faec318c27c1f6d7518acdf384d5f5a8c1453aa)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n","severity":"medium","status":"open","source":"osv","source_url":"https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised","labels":["GHSA-2v46-p5h4-248w"],"created_at":"2026-04-19T04:30:29.782210+00:00","updated_at":"2026-04-19T04:30:29.782210+00:00"}],"total":21,"_cache":"miss"}