TrueGether is an eBay alternative built around a zero-fee model for sellers. This post's about the Listing Details page: the single page every buyer lands on before deciding whether to buy something on TrueGether, and the one we were most nervous about touching.
We rebuilt it in React, Vite, TypeScript, and Tailwind. The stack decision wasn't the hard part. What actually took the time was everything the old page was quietly doing that nobody had written down anywhere.
What the old page was actually carrying
The pattern is probably familiar to anyone who's rebuilt a page that's been patched for years: small fixes accumulate into undocumented behavior. Small fixes can accumulate into undocumented behavior: a spacing rule that only matters for one product category, or logic that was added for an old edge case and never removed because nobody was sure what would break.
Why Vite mattered more than we expected
The concrete effect was on how willing people were to iterate during review. A slow feedback loop doesn't just cost time, it changes behavior — people stop trying small improvements when every attempt costs thirty seconds of waiting.
TypeScript found problems that weren't type problems
This was the real surprise. Adding types to a page handling prices, variants, inventory, and seller data didn't just catch mismatches — it forced us to actually agree on what shape that data was supposed to be. The important part wasn't any single mismatch. It was that the type system forced us to make assumptions explicit instead of letting them remain implicit. The type system didn't cause those problems. It just made them impossible to keep ignoring.
The Tailwind migration cost was about unlearning, not learning
The class-name syntax isn't the hard part of adopting Tailwind. The hard part is years of CSS instinct — reaching for a new stylesheet rule instead of composing utility classes — not disappearing just because the tooling changed.
What we'd do differently
The risk in a rewrite like this was never really the new code — it was the undocumented behavior sitting in the old code that nobody had mapped out. That's the main lesson we're carrying into the next piece of TrueGether's infrastructure we touch: map it before you migrate it, not during.
Top comments (0)