WhatBrokeToday
FAQ
Today's Trends
mediumInvestigatingBunv0.1.2

Bun Plugin Tailwind 0.1.2 Emits Invalid Drive-Qualified Asset Paths on Windows

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

Executive summary

On Windows, bun-plugin-tailwind 0.1.2 treats drive-qualified source paths as relative paths using POSIX rules, causing CSS asset paths to incorrectly climb out of the drive and fail builds. The issue specifically affects Windows environments, while macOS and Linux builds succeed.

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

The plugin rebasally emits relative CSS url() using POSIX path rules on Windows, transforming drive-qualified paths into broken relative paths like ../../../../../../../H:/...

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    bun-plugin-tailwind: Windows drive-qualified CSS asset paths become ../../…/C:/… and fail to resolve(opens GitHub issue in a new tab)

    What happens On Windows, bun-plugin-tailwind 0.1.2 emits a relative CSS url() rebased with POSIX path rules, so a drive-qualified source path is treated as a relative path and the URL climbs out of the drive: background-image:url("../../../../../../../H:/…/images/probe.svg") Bun then fails the build because that relative URL does not exist. The same stylesheet builds correctly on macOS and Linux. Where this belongs The published package's metadata points at tailwindlabs/tailwindcss…

    by mq1n 0upvotes 2comments

Timeline

  1. First report on GitHub issue

    bun-plugin-tailwind: Windows drive-qualified CSS asset paths become ../../…/C:/… and fail to resolve

    Source