-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[v4] Tailwind CLI ignores .gitignore in watch mode #15684
Comments
I assume watch mode also picks up Edit: As mentioned below by @wongjn this is expected for the old values to stay in output.css, this comment can be ignored, but the initial issue is still valid. |
@wongjn you're right, let's forget that the old values stays in output.css. Still, the data in .gitignore file should be respected to prevent watching for ignored files/directories. |
This is a big problem if you work on an app that logs periodically, s. rails/tailwindcss-rails#491 (comment). |
Tailwind is also watching |
What version of Tailwind CSS are you using?
v4.0.0-beta.9
What build tool (or framework if it abstracts the build tool) are you using?
@tailwindcss/cli@4.0.0-beta.9
What version of Node.js are you using?
$ node --version
v23.5.0
What browser are you using?
N/A
What operating system are you using?
macOS
Reproduction URL
Describe your issue
When tailwindcss cli is running in watch mode and ignored file is modified the output will contain css from the ignored file:
To reproduce:
output.css
doesn't haveh-100
$ cat output.css | grep h-1 $
test.go
and observe tailwindcss cli logoutput.css
now haveh-100
$ cat output.css | grep h-1 .h-100 {
The text was updated successfully, but these errors were encountered: