Replies: 2 comments
-
I would also suggest making the color decision stable. At the moment, because of the randomness, a turborepo containing a single workspace (not very useful, but you have to start somewhere) gets a (potentially) different color every time a command is executed. A stable coloring option suggestion would be to hash the package.json name, reduce this information to a given number of bits, and use it as the index of a color table. In any case, for projects with more workspaces than color options, there will be duplication. The use of a larger color palette (eg: 256 colors, or the full 24bit RGB color space) may solve that, at the expense of compatibility (not all TTYs can render those colors) and accessibility (colors may not be contrasted enough on an unknown terminal background color). Edit: the color is not random, but is based on the cache hash, with 5 possible color values: |
Beta Was this translation helpful? Give feedback.
-
A lot has changed since this Discussion was made but I'll close this in favor of #2564. P.S. There's a new terminal UI in 2.0 to try out where this wouldn't be so much of an issue. |
Beta Was this translation helpful? Give feedback.
-
Right now each package gets a random color when you run something like
turbo run build
, which means sometimes 2 packages will have the same color (see picture,docs
andclient
look the same). This is a really minor thing but it would be nice to see each package differentiated better at a glance by making sure there are no duplicates 🙏 tyBeta Was this translation helpful? Give feedback.
All reactions