-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
tailwind --watch randomly does not update the output CSS (Likely only when saving through SSH) #7467
Comments
In I think this gets solved if this is set the same as
The explanation is written in this section for reference. |
I've changed the above
without the conditional and it's working well when uploading the watched file in Relevant changes in the previous PR on Windows. |
The currently defined The value was meant to be for tailwindcss/src/cli/build/watching.js Line 35 in 5ea752e
Perhaps |
What version of Tailwind CSS are you using?
v3.0.22
What build tool (or framework if it abstracts the build tool) are you using?
Tailwind command and a pug file.
What version of Node.js are you using?
v16.14.0
What browser are you using?
N/A
What operating system are you using?
Ubuntu 20.04
Reproduction URL
tailwind.config.js
test.pug
Describe your issue
With the above 2 file setup on a remote server, I run,
tailwind --output tailwind.css --watch --content './test.pug'
it outputs the file fine and subsequently, I edit the pug file on the server locally via
vim
and change.bg-green-100
to.bg-green-200
and so on, the output CSS has them appended just fine.But if I try to upload the file from my machine to the remote server through SSH (as in upload on save feature of an editor, IntelliJ to be specific) to edit the pug file, it seems the update only happens sporadically even though the
tailwind
command saysRebuilding...
with no errors on each upload.Perhaps it's something to do with the timing the tailwind receives the file system notification but the file isn't exactly updated right at the moment for it to pick up the change?
The text was updated successfully, but these errors were encountered: