Colour Shades Support

[catuhana]

Generate colour shade based on the colour dynamically, like Tailwind's colour shades (though, Tailwind's are hand-picked). There was an attempt at #34.

[catuhana]

I don't think that's a feature definitely needed, but it would be good to have. Contributions are welcome.

[catuhana]

I forgot to comment here, but @catppuccin/palette@2.0.0-beta.1 has colour tints.

[ELHart05]

I'd like to take this on. I wanna proposed the following design feedback before I implement:

• Opt-in shades?: boolean option (default false, so existing output/bundle size is unchanged).
• When enabled, each colour becomes { DEFAULT: , 50…950: } (Tailwind stops), base stays as DEFAULT.
• Generation: scale lightness in OKLCH keeping hue/chroma, so steps are perceptually even. The palette already ships hsl, so I can do this dependency-free; alternatively culori (used in Add Colour Shades Support #34) for OKLCH. Do you prefer zero-dep HSL, or a small colour lib for OKLCH?

Also I wonder which stop set (50–950?), and should the base also map onto the nearest numbered stop or only DEFAULT?

[catuhana]

I'd like to take this on. I wanna proposed the following design feedback before I implement:

• Opt-in shades?: boolean option (default false, so existing output/bundle size is unchanged).
• When enabled, each colour becomes { DEFAULT: , 50…950: } (Tailwind stops), base stays as DEFAULT.
• Generation: scale lightness in OKLCH keeping hue/chroma, so steps are perceptually even. The palette already ships hsl, so I can do this dependency-free; alternatively culori (used in Add Colour Shades Support #34) for OKLCH. Do you prefer zero-dep HSL, or a small colour lib for OKLCH?

Also I wonder which stop set (50–950?), and should the base also map onto the nearest numbered stop or only DEFAULT?

Thanks for your interest!

• I think shades should always be there.

• I don't think we need to generate them manually:

  I forgot to comment here, but @catppuccin/palette@2.0.0-beta.1 has colour tints.

  I think we should use the beta version? It shouldn't be breaking for us.

• If we use @catppuccin/palette beta, stop sets should be determined by how many colour tints there are.

[catuhana]

BTW, beta is in the feat/generate-tints-and-shades branch. It's a bit outdated, but it should be fine? The main branch (which is also released as v1.8.0 right now) has added oklch colour space, so it may be better to generate accurate shades ourselves using culori maybe? I can't decide, open to hear your opinions.