---
title: "Discussion on \"Solid 2.0 Hands-On: The Same Small App Ships Four Times the JavaScript.\" | Hashnode"
description: "Discussion on \"Solid 2.0 Hands-On: The Same Small App Ships Four Times the JavaScript.\". Solid 2.0 is here after five years, and its announcement reads like a framework growing up: async inside the reactive graph, server functions in the core, diagnostics that catch your mistakes as you m"
url: "https://hashnode.com/posts/solid-2-0-hands-on-the-same-small-app-ships-four-times-the-javascript/6afd017ae3c5a20f63ec988f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Solid 2.0 Hands-On: The Same Small App Ships Four Times the JavaScript.](https://aheadkit.hashnode.dev/solid-2-0-hands-on-the-same-small-app-ships-four-times-the-javascript?utm_source=hashnode&utm_medium=feed)

Solid 2.0 is here after five years, and its announcement reads like a framework growing up: async inside the reactive graph, server functions in the core, diagnostics that catch your mistakes as you m

17h ago · 5 min read · aheadkit.hashnode.dev  
Read the article

-   [#solidjs](https://hashnode.com/tag/solidjs)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#frontend](https://hashnode.com/tag/frontend)

## Written by

[Abdus Salam](https://hashnode.com/@aheadkit)

@aheadkit

  
[View profile](https://hashnode.com/@aheadkit)

## Responses 2

Markdown supported · ⌘↵ to post

[Alex Yu](https://hashnode.com/@alexyu)

[9h ago](https://hashnode.com/posts/solid-2-0-hands-on-the-same-small-app-ships-four-times-the-javascript/6afd017ae3c5a20f63ec988f/comment/6afd668c889eb843a5e60f22)

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.

[Abdus Salam](https://hashnode.com/@aheadkit)

[8h ago](https://hashnode.com/posts/solid-2-0-hands-on-the-same-small-app-ships-four-times-the-javascript/6afd017ae3c5a20f63ec988f/comment/6afd668c889eb843a5e60f22#reply-6afd7fd2df4fd796e0fc96c1)

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?
