Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the watcher does not work when adding a custom style to tailwind #13905

Closed
dimiatr opened this issue Jun 27, 2024 · 1 comment
Closed

the watcher does not work when adding a custom style to tailwind #13905

dimiatr opened this issue Jun 27, 2024 · 1 comment

Comments

@dimiatr
Copy link

dimiatr commented Jun 27, 2024

"tailwindcss": "^3.4.4"

For example: v2.0.4

I don't use any.

For example: postcss-cli 8.3.1, Next.js 10.0.9, webpack 5.28.0

v20.14.0

For example: v12.0.0

Firefox

For example: Chrome, Safari, or N/A

Windows 10

For example: macOS, Windows

https://play.tailwindcss.com/MHLQaZ7rcK?file=config

A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.

the watcher does not work when adding a custom style to tailwind

I encountered such a problem that when I enter custom properties into tailwind.config.js file, for example, in colors I enter new colors firmBlack: "#333", which I need and they do not appear in html file, when I explicitly specify a class, for example text-firmBlack, it is not applied.

but if I exit vsCode and log in again, everything works, has anyone encountered this problem? it is not profitable to restart vsCode each time

Maybe it's a general glitch, it happened only today, yesterday it didn't happen.

@dimiatr
Copy link
Author

dimiatr commented Jun 30, 2024

It wasn't about tailwindcss
It was a Windows account issue, fixed everything by literally changing the account

@dimiatr dimiatr closed this as completed Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant