chore: replace chalk with colorette

[JounQin]

Will use picocolors later maybe after alexeyraspopov/picocolors#79 been really fixed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0f46b4d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@unts/patch-package	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/property-expr@1.5.1	CVE: GHSA-6fw4-hr69-g3rv Prototype Pollution in property-expr (CRITICAL) Affected versions: < 2.0.3 Patched version: 2.0.3	yarn.lock	⚠︎
Critical CVE	npm/simple-git@1.132.0	CVE: GHSA-9w5j-4mwv-2wj8 Remote code execution in simple-git (CRITICAL) Affected versions: < 3.16.0 Patched version: 3.16.0	yarn.lock	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/property-expr@1.5.1
• @SocketSecurity ignore npm/simple-git@1.132.0

[socket-security]

Report too large to display inline

View full report↗︎