Virtual bundle size impact
An application using a framework adapter also includes virtual core. The table therefore shows the combined payload users evaluate, rather than presenting the smaller adapter file by itself.
| Package | raw | min | minGz | minBrotli |
|---|---|---|---|---|
| Core only | 17.8 kB | 17.3 kB | 6 kB | 5.41 kB |
| Core + lit | 22.2 kB | 21 kB | 7.09 kB | 6.4 kB |
| Core + preact | 20.3 kB | 19.1 kB | 6.82 kB | 6.16 kB |
| Core + react | 23.6 kB | 19.4 kB | 6.92 kB | 6.24 kB |
| Core + solid | 21.2 kB | 19.8 kB | 7.11 kB | 6.41 kB |
| Core + svelte | 20.2 kB | 19.2 kB | 6.75 kB | 6.09 kB |
| Core + vue | 21 kB | 19.7 kB | 7.08 kB | 6.39 kB |
How the numbers are produced
The website build first builds the current workspace packages, reads their published ESM exports, minifies with SWC, and generates raw, gzip, and Brotli sizes. Peer frameworks such as React, Vue, or Lit are external and are not included.
Core and adapter files are measured separately and added in the table. This is a conservative compressed estimate: a final application bundle may compress shared tokens together and tree-shake unused exports. Use these values to compare adapter impact, then measure the production application for an exact result.