You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like minimum node version for v3 will be 20.19 which means we could remove a dependency and instead use the built in node:util#styleText fn - there is only one bug that isn't patched until v22 which is that nested styleText calls won't colour correctly, but that's only issue for the codebase and shouldn't effect consumers of changesets, so could still be worth it.
imo we can bump the minimum node version to 22 since 20 became EoL this weekend.
my opinion on styleText is mixed, and i think it should wait until after #1879, but my opinions are not strong enough to stop anyone from implementing it :)
it is built-in 👍
i strongly dislike the api 👎 (can be fixed with a small wrapper)
it's quite a bit slower 👎 (but not noticably iirc)
Happy to wait, and we can definitely add a small wrapper to make it more like picocolors. I didn't realise it was slower, that's a shame, but yea I don't think it's noticeable and so it's still likely worth it IMO.
Activity
Andarist commentedon May 3, 2026
cc @beeequeue
beeequeue commentedon May 4, 2026
imo we can bump the minimum node version to 22 since 20 became EoL this weekend.
my opinion on
styleTextis mixed, and i think it should wait until after #1879, but my opinions are not strong enough to stop anyone from implementing it :)it is built-in 👍
i strongly dislike the api 👎 (can be fixed with a small wrapper)
it's quite a bit slower 👎 (but not noticably iirc)
ghostdevv commentedon May 4, 2026
Happy to wait, and we can definitely add a small wrapper to make it more like picocolors. I didn't realise it was slower, that's a shame, but yea I don't think it's noticeable and so it's still likely worth it IMO.
bluwy commentedon May 13, 2026
Closed by #2004