feat: Replace chalk with picocolors

[ishon19]

Summary

This PR is for replacing the chalk package in the codebase with lighter and faster picocolors owing to the small bundle size (~5Kb) of picocolors as compared to the existing chalk (~48Kb).

Test plan

🚧 WIP

Fixes #15189

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ishon19 / name: Shreyans Pathak (820347e, 95365f5, bddbdb6, 90fa15c, 9175c29, 69e103d, 19a4639, b853195, 0900fd3, 0511891, 2f362e5, 0b2a7fc, b848788, ec3cb59, 0fd1645, d32505e, 87fb3f3, daf6648, 1e7f0e8, 9e09d89, cc0f080, 964e3ae, 73a4051, 47542f6, 51baa3e, e204454)

[netlify]

✅ Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	73a4051
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/66fb05e1e8fb280008ada0ec
😎 Deploy Preview	https://deploy-preview-15197--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mrazauskas]

Probably supports-color can be also replaced by .isColorSupported from picocolors:

jest/packages/jest-worker/src/workers/ChildProcessWorker.ts

Line 11 in 213c3b2

import {stdout as stdoutSupportsColor} from 'supports-color';

[ishon19]

Probably supports-color can be also replaced by .isColorSupported from picocolors:

jest/packages/jest-worker/src/workers/ChildProcessWorker.ts

Line 11 in 213c3b2

import {stdout as stdoutSupportsColor} from 'supports-color';

That makes sense, thanks for pointing it out! :)

[SimenB]

this might be a bit late, but maybe it helps? es-tooling/module-replacements-codemods#77

[ishon19]

this might be a bit late, but maybe it helps? es-tooling/module-replacements-codemods#77

Much helpful, thanks for sharing @SimenB!

Planning to wrap the changes up ASAP, right now stuck on yarn build failure as API extractor complains about missing d.ts type declaration file in picocolors as in the screenshot below, which they do have, but it's called picocolors.d.ts and I suspect api-extractor is picking up the wrong file, trying to override that behavior in bundleTs.mjs.

[mrazauskas]

@ishon19 This looks like a picocolors bug. They are shipping .ts file instead of .d.ts to npm, but a package should only have .js and .d.ts.

I mean, if code is compiled using tsc, these are the only files one will have in a package.

[ishon19]

@ishon19 This looks like a bug Picolors. They are shipping .ts file instead of .d.ts to npm, but a package should only have .js and .d.ts.

I mean, if code is compiled using tsc, these are the only files one will have in a package.

Thanks @mrazauskas, yes I agree, I can create an issue on their repo for clarification.

[Kocal]

Hi everyone, I'm really interested with this PR!

@ishon19, have you had any time recently to get things moving? 🙏🏻

[mrazauskas]

@Kocal If I get it right, this PR is still block because of alexeyraspopov/picocolors#77

[Kocal]

Thanks @mrazauskas!

[ishon19]

Hi everyone, I'm really interested with this PR!

@ishon19, have you had any time recently to get things moving? 🙏🏻

Thanks @Kocal, I know it's waiting for too long and I don't know when the issue this is waiting on is going to be resolved, so if you have any workaround or a better idea to make this happen, please feel free to link a new PR. :)

[Kocal]

Hey @ishon19, don't worry, I wasn't trying to blame you or something like that, I'm just super hyped by your PR because I also want to replace chalk by picocolors (see symfony/webpack-encore#1333 & nuxt/friendly-errors-webpack-plugin#21).

I would be really happy to help here, I will take a look today, thanks :)

[ishon19]

I would be really happy to help here, I will take a look today, thanks :)

Yeah, absolutely! Since you worked on similar issues, really appreciate your feedback :)

[Kocal]

alexeyraspopov/picocolors#82 has been merged

[ishon19]

alexeyraspopov/picocolors#82 have been merged

@Kocal Thanks for the update and the fix as well!

[alexeyraspopov]

@Kocal this change is now available in v1.1.1

[Kocal]

@alexeyraspopov thanks! :)

[ishon19]

Hey @Kocal! Since we have the official confirmation now, I believe we're all set for the upgrade!

Unfortunately at this moment, I've got a lot on my plate and I don't want to delay this upgrade any further, please feel free to take this forward if you'd like to. You can open a new PR altogether, or use this one. Let me know if I can help in any way. Appreciate your help :)