Are any of these goona get fix eventually in v4?

[babakfp]

1. Syntax highlighting:

2. Color change:

also there is issue and a reason that I don't directly use color varialbes...

none of these issues existed in v3. the whole code suggestion is also pretty slow and sometimes it need to recalculate or something and it's frasturating.

[RobinMalfait]

1. What theme are you using here? Also make sure that you are using the Tailwind CSS language mode and not CSS.

2. What's the issue with this?

Is it because you hardcoded the colors and don't want that? Normally you don't often change these values so I don't immediately see the issue here.

also there is issue and a reason that I don't directly use color varialbes...

Can you share more about this, I would like to understand the issues you are referring to.

none of these issues existed in v3

You can still use Tailwind CSS v3 if you want!

the whole code suggestion is also pretty slow and sometimes it need to recalculate or something and it's frasturating.

It's heavily cached, but it will indeed re-compute from scratch when you make changes to your CSS file and any of its dependencies (@import, @plugin, …).

If you don't like this feature, then you can turn it off: https://github.com/tailwindlabs/tailwindcss-intellisense#tailwindcsslintsuggestcanonicalclasses

---

In general, next time let's open an issue / discussion per individual topic so it's easier to track if changes need to be made.

[babakfp]

What theme are you using

Dark Modern

make sure that you are using the Tailwind CSS language mode and not CSS.

I did know about this one, and yeah it was on "CSS" (I had it changed some time ago), after switchign to the right langauge, syntax highlighting still has huge issues:

update:

for some reason syntax highlighting for this one decided to work:

but some other like this still doesn't:

this time closed/reopened to not be surprised again...

2. What's the issue with this?

Using a different gray color and changing color variables is something that is done often; you need a lot of bloat to get that done.

In v3 it was easy and simple with no bloat. you would just import default colors and do gray: colors.zinc.

There was some arguments given by tw team for not adding a syntax like --color-gray-*: --color-gray-* for this. by at the same time we have the same syntax for unregistering default variables (using --color-zinc-*: initial;).

Well, at this point the best alternative would be to just use zinc keyword in class names instead of insisting on gray. but, there is one big issue with that. i have had migrated my site gray color from one to another. and did that very easily and it didn't need any class name migration. so, using it's a big no for me and probably for others too for the same eason.

Can you share more about this, I would like to understand the issues you are referring to.

#17460

You can still use Tailwind CSS v3 if you want!

:| no i don't want to use v3 but v3 in ways was much better than v4:

• js plugin system instead of new made up (ugly, hard to read, confusing, needs learning and limited) syntax.
• you had a real programming langauge to take advantage of in a config file instead of limited css. i can still use js plugin system? this just shows new system is bad and also not ready, other ways there should be two ways to do the same thing!
• syntax highlighting worked (with vscode postcss plugin)
• [IntelliSense] When sorting, give priority to `justify-between` instead of `justify-baseline` if possible. #17354 there is a whole bunch of things like this. there is no finetuning on some suggestions that makes it super annoying. classes that you never use gets suggested before classes used all the time.
• probably some other that i don't remember.

i'm still frasturated with some tw 4 because of some of these bad ideas/opinions...

It's heavily cached, but it will indeed re-compute from scratch when you make changes to your CSS file and any of its dependencies (@import, @plugin, …).

some times it just does it for no reason and i need to sit there and wait ~5-10s 🤷‍♂️

If you don't like this feature, then you can turn it off: https://github.com/tailwindlabs/tailwindcss-intellisense#tailwindcsslintsuggestcanonicalclasses

idk, it's a useful feature 🤷‍♂️

---

@utility outline-inset {
    @apply -outline-offset-2;
}

this is false positive, it's not true. outline-inset exists because of custom @utility outline-inset.

---

tnks for taking a look