Inside Ionify — An engineering experiment with virtual compiler inputs, build artifacts, and correctness-aware invalidation.
A few days ago, I shared a Tailwind performance regression in Ionify, my open-source frontend build tool.
A developer reported that changing Tailwind classes could trigger a full rescan.
In the affected workload, a 100-file-change build increased from approximately 300ms to 1.3s.
Our first optimization reduced the measured overhead by around 40–50% .
That was encouraging.
But it raised another question:
Could we eliminate the unnecessary full rescan instead of continuing to make it progressively cheaper?
1.…