Replies: 4 comments
-
Possible cause:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey! Were you able to update to Tailwind CSS v4 and check if that's still an issue there? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sorry, I haven't touched frontend since September last year :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
@kbr- Haha fair! I'm going to move this to a discussion for now then. 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of Tailwind CSS are you using?
3.4.10,
tailwindcss-linux-x64
binary downloaded for the releases page.What operating system are you using?
Reproduction + description
You need two empty files: empty config.js file and empty input.css file; they must be in separate directories. You can execute the following sequence of bash commands to reproduce:
mkdir repro cd repro mkdir cfg touch cfg/config.js touch input.css wget https://github.com/tailwindlabs/tailwindcss/releases/download/v3.4.10/tailwindcss-linux-x64 chmod +x tailwindcss-linux-x64 ./tailwindcss-linux-x64 -c cfg/config.js -i input.css -o output.css -w
Then open the file
input.css
invi
and save it (:w
).Tailwind will not rebuild the file on save.
The conditions to reproduce the issue are oddly specific:
touch input.css
causes rebuildgedit
and saving causes rebuild-p
(--poll
), saving invi
works (causes rebuild):config.js
from the same directory asinput.css
, saving invi
works:Why
vi
is needed? I'm guessing it's somehow related to the file metadata, perhaps saving invi
is not modifying some file metadata thattouch
or saving with another editor likegedit
does, and-w
is observing this metadata. I'd guess there are some other editors which make this possible to reproduce.But why do the files have to be in different directories? No idea.
Beta Was this translation helpful? Give feedback.
All reactions