The vite-plugin-solid peer requirement catch is useful, I'd have hit that exact wall. Did the 59 kB figure change at all once you tree-shook the build, or is most of it the new reactive core? Curious whether the gap shrinks on a bigger app.
Glad the plugin catch saved you that wall — it cost me an hour before I found the right plugin. The 59.84 kB is already the production build, and Vite tree-shakes that by default, so there's no separate un-shaken number underneath it. What I didn't do is pull the bundle apart, so I can't honestly say how much is the new reactive core versus the extra packages — server functions and the rest ship whether this little app uses them or not. Haven't run a bigger app yet, and that's the measurement that would answer your second question; my guess is the gap shrinks in percentage terms, since the framework cost stays roughly fixed while your code grows, but that's a guess, not a number. Going to run that one on a bigger app and see where the gap actually lands — what would you call a fair test, routing and a few real pages, or something bigger?