It's time to fix the Tailwind CSS deprecated colors warning when using tailwindcss/colors

[Christian-Garrison]

warn - As of Tailwind CSS v2.2, `lightBlue` has been renamed to `sky`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `warmGray` has been renamed to `stone`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `trueGray` has been renamed to `neutral`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `coolGray` has been renamed to `gray`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `blueGray` has been renamed to `slate`.
warn - Update your configuration file to silence this warning.

Simply using tailwindcss/colors seems to cause this error even when not directly using any deprecated color in the tailwind config (i.e. lightBlue, warmGray, trueGray, coolGray, blueGray).

import tailwindcolors from 'tailwindcss/colors';

export const colors = {
  ...tailwindcolors,
  gray: {
    50: '#fafafa',
    100: '#e6e8e7',
    200: '#d9dbdb',
    300: '#b3b8b7',
    400: '#9a9f9e',
    500: '#808785',
    600: '#676f6e',
    700: '#4e5856',
    800: '#343f3d',
    900: '#1b2826',
    950: '#020f0d',
  },
  teal: {
    50: '#d9f2ef',
    100: '#b8e6e1',
    200: '#a0ddd7',
    300: '#70cdc2',
    400: '#41bcae',
    500: '#11ab9a',
    600: '#0d8679',
    700: '#0a675c',
    800: '#07443e',
    900: '#03221f',
    950: '#020f0d',
  },
};

import { type Config } from 'tailwindcss';
import { tokens } from './src/tokens';

const config = {
  darkMode: ['class'],
  content: ['./src/**/*.{js,jsx,mdx,ts,tsx}'],
  prefix: '',
  theme: {
    extend: {
      colors: {
        primary: tokens.colors.teal,
        gray: tokens.colors.gray,
      },
    },
  },
  // ...
} satisfies Config;

export default config;

When stating warn - Update your configuration file to silence this warning. is there a way to fix this, if so it isn't blatantly documented in the official docs?

At the least, there should be an option in the config to silence these warnings completely without needing to actually apply any changes, basically an option to forcefully say "We understand and don't want these logs even if it is an actual issue so we can just get rid of them." suppressDeprecationWarnings

Additionally I'm confused why something deprecated is included just to log these warnings to users, why not include an auto migration warning to those upgrading versions "this seems to be the typical standard in upgrading these days, right?"? Also why not give additional options within tailwindcss/colors to import the deprecated colors directly for those that need the backwards compatibility bandaid instead of "punishing" users on the latest versions.

import {  deprecatedColors } from 'tailwindcss/colors';

These suggested fixes reward the new & latest version users the ability to use the default colors from tailwindcss/colors freely without being warning punched, since these users are less likely to even know those deprecated colors exist.