Sample
Pinpoint Chalk's malformed `hex()` input behavior when nullish values and malformed strings are provided.
sha256:8a0531ffe818e26b9036a49be7c8f41af3ee24f2802f62aa006deb0ac042b7dd
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Pinpoint Chalk's malformed `hex()` input behavior when nullish values and malformed strings are provided. HOW
- Packages
- chalk 6.0.0
- Environment
- node
- Created
- 2026-08-17T03:15:58Z
Commonly assumed
A caller should get the same kind of rejection for all obviously malformed `chalk.hex(...)` inputs.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- With `chalk.level = 3`, calling `chalk.hex('not-a-color')('x')` returns `x` wrapped in `\u001b[38;2;0;0;0m` and `\u001b[39m` and does not throw.
- `chalk.hex('')('x')` also returns black 24-bit ANSI output instead of an error.
- Nullish inputs are the only values that fail here: `chalk.hex(null)('x')` and `chalk.hex(undefined)('x')` throw TypeError while malformed strings do not.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9