tailwindcss cli leaves hidden files in /tmp

[willoma]

What version of Tailwind CSS are you using?

v4.0.12.

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

Only the tailwindcss cli.

What version of Node.js are you using?

None

What browser are you using?

Not relevant

What operating system are you using?

Ubuntu Linux 24.04

Reproduction URL

Not relevant

Describe your issue

$ ls -a /tmp/.*.node
ls: cannot access '/tmp/.*.node': No such file or directory
$ tailwindcss
≈ tailwindcss v4.0.12

Usage:
[blah blah doc etc]
$ ls /tmp/.*.node
/tmp/.19abdddb78ffefff-00000001.node  /tmp/.5effdedebd9bdffd-00000000.node  /tmp/.dd2f9cfefaefccbe-00000002.node

[RobinMalfait]

Hey!

This seems like a side effect of using native tools with .node files. We don't put anything in the tmp folder ourselves. Is this causing actual issues, or is this just something you noticed?

[willoma]

It creates 3 files each time I run it. It already filled my root disk twice. At least now I know where to look when the disk is full, but it's annoying, to say the least.

Just now:

$ ls -lh /tmp/.*.node | wc -l
446
$ du -shc /tmp/.*.node | tail -n 1
1,7G    total

[philipp-spiess]

@willoma Oof, thats a lot! Are you using the Standalone CLI or the @tailwindcss/cli npm package?

My guess to what's happening here is that Bun (which we use for the Standalone CLI) bootstraps the environment to load the bundled .node extensions into /tmp on Linux and that's not cleaned up correctly 🤔

[willoma]

I'm using the standalone CLI downloaded from https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.0.12.

I am using another process to watch files modifications, which runs tailwindcss each time styles need to be reloaded.

I tried running tailwindcss with the --watch parameter, but it reads files that should not be parsed (ie. Go source code), even though they are explicitly excluded in tailwind.config.scss:

@import "tailwindcss" source(none);
@import "./http/styles/colors.css";
[...]

@source "http/*.templ";
[...]

[philipp-spiess]

Created an upstream issue: oven-sh/bun#19550

[philipp-spiess]

Hey! Good news, the upstream issue was resolved. We'll create a release with the updated version of bun soon. Thanks for the report!