WhatBrokeToday
FAQ
Today's Trends
mediumInvestigatingBunv1.4.4+38afee6c8

Bun bunx on Windows Reuses Incomplete TEMP Installs Resulting in Module Errors

  1. Investigating(current)
  2. Trending(upcoming)
  3. Workaround available(upcoming)
  4. Resolved(upcoming)

Executive summary

On Windows, bunx reuses incomplete or partially cleaned TEMP directory installs when Disk Cleanup removes older files, leading to 'Cannot find module' errors. The issue affects Bun version 1.4.4+38afee6c8 and later on Windows platforms.

No verified workaround yet

None of the linked reports describe a mitigation. Follow this incident to hear when one appears.

Official fix
Technical root cause

Disk Cleanup's 'Temporary files' handler deletes files in %TEMP% based on access dates, leaving hard links and incomplete trees that bunx subsequently attempts to reuse.

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    bunx on Windows reuses incomplete TEMP installs after cleanup ("Cannot find module")(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4+38afee6c8 What platform is your computer? Microsoft Windows NT 10.0.26300.0 x64 What steps can reproduce the bug? On Windows, bun x installs into %TEMP%\bunx-<id>-<package>. In my tests the package files there are hard links to the install cache, so they have the dates of the cache files: a tree made today from cache entries extracted a month ago looks a month old. Disk Cleanup's "Temporary files" handler deletes files in %TEMP% last accessed more than 7…

    by dennev 0upvotes 0comments

Timeline

  1. First report on GitHub issue

    bunx on Windows reuses incomplete TEMP installs after cleanup ("Cannot find module")

    Source