[Performance] Memoize shouldDisplayColors

[gonzaloriestra]

WHY are these changes introduced?

High-frequency logging paths call shouldDisplayColors repeatedly to determine if output should be colorized. Accessing process.env and checking TTY status on process.stdout involves small but measurable overhead that adds up over the lifecycle of a CLI command, especially when debug logging is enabled or many messages are processed.

WHAT is this pull request doing?

This PR introduces memoization for the shouldDisplayColors function in @shopify/cli-kit.

• Results are cached in a module-level variable when called with the default process object.
• Custom process objects (e.g., used in unit tests) bypass the cache to ensure isolation and correct behavior during testing.
• The logic remains identical, preserving current behavior while improving efficiency for the common case.

How to test your changes?

CI

Post-release steps

None.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

---

PR created automatically by Jules for task 303941856508991664 started by @gonzaloriestra

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.