Releases: marvinhagemeister/kolorist
1.8.0 - TrueColor support
Minor Changes
-
737ef18: Add support for 24bit TrueColor detection.
TrueColor is supported in every modern terminals these days. The exception to that is the built in Terminal app on macOS and CI systems. TrueColor values are automatically converted to Ansi 256 when TrueColor isn't supported. The only case where I found that in practice was with Terminal.app on macOS which only supports Ansi 256.
This also fixes an issue when a terminal would declare support for TrueColor, but not Ansi 256. Previously, we'd completely strip colors when printing Ansi 256 despite that being supported. This release addresses that.
1.7.0
What's Changed
- fix: handle
NO_COLOR
by @privatenumber in #20 - fix: support
FORCE_COLOR=2,3
by @privatenumber in #21 - test: use esbuild to run by @privatenumber in #23
- docs: use screenshot with function names by @privatenumber in #22
- Setup changesets by @marvinhagemeister in #24
New Contributors
- @privatenumber made their first contribution in #20
Full Changelog: v1.6.0...v1.7.0
1.6.0
What's Changed
- Fix: add types to exports field to compat nodenext module resolution by @otakustay in #14
- Update package.json exports by @marvinhagemeister in #15
1.5.1
What's Changed
- Update exports field in
package.json
by @sidwebworks in #12
New Contributors
- @sidwebworks made their first contribution in #12
Full Changelog: v1.5.0...v1.5.1
1.5.0
Features
- Check for CI variable during color detection (#9, thanks @marvinhagemeister)
Maintenance
- Enable GitHub CI workflow (#10, thanks @marvinhagemeister)
- Rename main
master
branch tomain
1.4.1
- Fix unable to bundle with esbuild es5 (#8, thanks @marvinhagemeister)
1.4.0
- Feature: Allow forcing color with FORCE_COLOR=1 (#7, thanks @BenoitZugmeyer)
1.3.2
- Fix: optional chaining isn't compiled away by TS as I thought (#5, thanks @bjarkihall)
- Always downtranspile to ES2019 for Node 12 support (thanks @marvinhagemeister)
1.3.1
This fixes a regression introduced earlier today with 1.3.0
.
- Fix: runtime error if
TERM
is not defined in env (#4, thanks @bjarkihall)
1.2.3
This release fixes a publishing error with 1.2.2.