Standalone CLI outputs "watchman not found"

[aptinio]

What version of Tailwind CSS are you using?

v4.0.0

What build tool (or framework if it abstracts the build tool) are you using?

standalone executable, specifically, tailwindcss-linux-x64

What version of Node.js are you using?

N/A

What browser are you using?

N/A

What operating system are you using?

Linux

Reproduction URL

https://github.com/aptinio/tailwind-linux-cli-watchman-issue

Describe your issue

1. Download https://github.com/tailwindlabs/tailwindcss/releases/download/v4.0.0/tailwindcss-linux-x64 into root of reproduction project
2. Run:

./tailwindcss-linux-x64 --input input.css --output output.css --watch

The following is included in the output, even if the standalone CLI successfully rebuilds the output when Tailwind classes are changed in index.html

sh: line 1: watchman: command not found

[verachell]

I see this too, using a different OS tailwind standalone binary ( linux-arm64 ). Here is the info on mine:

What version of Tailwind CSS are you using? v4.0.0

What build tool (or framework if it abstracts the build tool) are you using? standalone executable tailwindcss-linux-arm64

What version of Node.js are you using? N/A

What browser are you using? N/A

What operating system are you using? Raspberry Pi running Debian

Reproduction URL: N/A

Describe your issue: a message comes up after I run my command ./tailwindcss --input in.css --output out.css --cwd .. --watch

sh: 1: watchman: not found

However, --watch still works because it rebuilds the css when classes are changed, and html output changes visually as expected.

In other words, the message sh: 1: watchman: not found is unexpected, but I do not see any loss in functionality.

[philipp-spiess]

Interesting! According to the docs of @parcel/watcher (the library we use for watching for file changes in the CLI), the watchman backend should only be selected if watchman is actually installed.

This function seems to run to check if watchman is installed: https://github.com/parcel-bundler/watcher/blob/119f1ff04bb41c2369929e37274900c61b0a9f49/src/watchman/WatchmanBackend.cc#L43-L66 any chance you have a WATCHMAN_SOCK variable in your shell?

[philipp-spiess]

Oh I misunderstood I guess if it still works this is just about the stdout being logged, possibly by this check right here: https://github.com/parcel-bundler/watcher/blob/119f1ff04bb41c2369929e37274900c61b0a9f49/src/watchman/WatchmanBackend.cc#L49

I think we can safely ignore this because in that case, @parcerl/watcher will fall back to another watcher. Maybe what we could do is create a bug report on the @parcel/watcher repo though if you want to silence this somehow. Does anyone of you want to look into that since you already have a system where this repros? (Ideally the repro for the parcel repository only uses @parcel/watcher and not tailwindcss).

[philipp-spiess]

I also decided to move this to a discussion, since it's not really a bug on the tailwindcss side since everything is still working as expected. Please let me know if that's not the case though and I misunderstood something 👍

[aptinio]

Thanks @philipp-spiess for pointing me in the right direction. 🙏

I agree, it's not a bug on the tailwindcss side. I took a stab at silencing the error upstream:
parcel-bundler/watcher#198