Skip to content

standalone executable creates 3 node files in temp folder every time it is run without cleaning up #18241

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

Closed
denniskaselow opened this issue Jun 6, 2025 · 1 comment

Comments

@denniskaselow
Copy link

denniskaselow commented Jun 6, 2025

What version of Tailwind CSS are you using?

v4.1.8

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

Standalone executable

What operating system are you using?

Windows 10

Describe your issue

Whenever I run tailwindcss it creates 3 .node-files in the C:\Users\<username>\AppData\Local\Temp-folder. They don't get cleaned up and accumulate. As shown in this gif:

Image

All three files are mostly binary data but contain "This program cannot be run in DOS mode." close to the start. Additionally, the smallest file contains:

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level='asInvoker' uiAccess='false' />
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

at the end, while the other two files contain something about some Rust crates in C:\Users\runneradmin\.cargo\registry\src\index.crates.io (there is no user runneradmin on my system).

@thecrypticace
Copy link
Contributor

Duplicate of #17114 (which was generally fixed)

These files are necessary to embed + run the native parts of our CLI (Oxide, Lightning CSS, and Parcel Watcher) on Windows and macOS (afaik, Linux can run them directly w/o writing to the filesystem first). Generally these get cleaned up after the program exits but on Windows I think the best that can be done here is cleaning them up after a reboot because of how it handles I/O and binaries loaded into a process.

If you reboot the files should disappear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants