Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

missing Tailwind 2.0 colors

See original GitHub issue

Hi, Thanks for this toolkit.

I have tried this: const colors = require('windicss/colors') in tailwind.config.js, but I see these typescript errors.

...
colors: {
       ...
        bluegray: colors.blueGray,
        coolgray: colors.coolGray,
        gray: colors.gray,
        truegray: colors.trueGray,
        warmgray: colors.warmGray,
        red: colors.red,
        orange: colors.orange,
}

Does windicss/colors' provide the full range of Tailwind 2.0 colors?

Issue Analytics

State:
Created 3 years ago
Comments:16 (11 by maintainers)

Top GitHub Comments

1reaction

FallDownTheSystemcommented, Feb 16, 2021

Probably unrelated but extending colors didn’t seem to work either.

module.exports = {
	darkMode: false,
	theme: {
		extend: {
			colors: {
				'test-orange': '#e05501'
			}
		}
	}
}

I’m not sure if this is intended behavior since the docs do say that “Any configuration options you provide will extend the default options.” but the migration guide still shows the theme > extend > colors format.

0reactions

antfucommented, Feb 17, 2021

It’s because uppercase in class names were ignored. Fixed now. Thanks.