refactor: replace chalk with picocolors

[escapedcat]

User description

• Replace chalk dependency with picocolors (~97% smaller)
• Update type definitions to use PicocolorsColor type
• Fix type error in format.ts by properly accessing color functions
• Keep ChalkColor as alias for backwards compatibility
• Replace chalk.grey with pc.gray (different spelling)

This reduces the direct chalk dependency from ~52KB to ~1.5KB while maintaining the same functionality.

---

PR Type

Enhancement

---

Description

• Replace chalk dependency with picocolors (~97% smaller)

• Update type definitions to use PicocolorsColor type

• Fix type errors in format.ts by properly accessing color functions

• Keep ChalkColor as alias for backwards compatibility

• Replace chalk.grey with pc.gray (different spelling)

---

Diagram Walkthrough

flowchart LR
  chalk["chalk (~52KB)"] -->|replace| pc["picocolors (~1.5KB)"]
  pc -->|update| types["PicocolorsColor type"]
  pc -->|fix| format["format.ts color access"]
  pc -->|maintain| compat["ChalkColor alias"]

Loading

File Walkthrough

	Relevant files
Enhancement	8 files format.ts Define PicocolorsColor type and update exports                      +31/-4    format.ts Replace chalk with picocolors and fix type errors                +18/-14  Question.ts Replace chalk with picocolors in color selection                  +3/-3      load-plugin.ts Replace chalk with picocolors in error logging                      +3/-3      InputCustomPrompt.ts Replace chalk with picocolors in render method                      +6/-6      format.ts Replace chalk with picocolors in format function                  +2/-2      get-prompt.ts Replace chalk with picocolors in prompt generation              +5/-5      meta.ts Replace chalk with picocolors in meta function                      +2/-2
Tests	2 files Question.test.ts Update test assertions to use picocolors                                  +5/-5      input.test.ts Update test to use picocolors instead of chalk                      +2/-2
Dependencies	5 files package.json Update dependency from chalk to picocolors                              +1/-1      package.json Update dependency from chalk to picocolors                              +1/-1      package.json Update dependency from chalk to picocolors                              +1/-1      package.json Update dependency from chalk to picocolors                              +1/-1      package.json Update dependency from chalk to picocolors                              +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Config-driven DoS Description: Dynamic property access pc[colorName] (derived from options.colors) is called as a function and, if a consumer supplies a non-color string (e.g., "proto" or any unknown key), it can yield a non-function and throw at runtime, enabling a configuration-driven denial-of-service by crashing formatting. format.ts [71-75] Referred Code const colorName: PicocolorsColor = colors[problem.level] || ("white" as const); const colorFn = pc[colorName]; const decoration = enabled ? colorFn(sign) : sign; const name = enabled ? pc.gray(`[${problem.name}]`) : `[${problem.name}]`;
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
🔴	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Unsafe color lookup: The new dynamic lookup pc[colorName] can be undefined at runtime (e.g., if options.colors contains an invalid string), causing a crash when invoked instead of gracefully falling back to a safe color function. Referred Code const colorName: PicocolorsColor = colors[problem.level] || ("white" as const); const colorFn = pc[colorName]; const decoration = enabled ? colorFn(sign) : sign; const name = enabled ? pc.gray(`[${problem.name}]`) : `[${problem.name}]`; Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.