AI summary by TwinMind
Solid.js Just Got WAY Better
Theo - t3․gg
13m 10s
SolidStart Framework Overview
- SolidJS described as React alternative focused on signals with high performance
- Mental model from React carries over well to Solid
- SolidStart = full-stack solution for building SolidJS apps (similar to Next.js)
- Manages backend, bundling, and infrastructure automatically
Historical Context and Evolution
- SolidStart launched early (not as early as Remix but earlier than many current frameworks)
- Initially built around Vite with custom server-side handling
- Vite originally focused on client bundles, not server solutions
- Two key groups emerged: Astro and Nuxt building backend-first solutions on Vite
- Community centralized on Astro as starting point
- SolidStart spent time "soul searching" for better maintainable experience
Nitro Integration - Major Architecture Change
- Nitro = project built around Vite to power Nuxt and other full-stack frameworks
- Think of it as starting point for building your own Next.js
- SolidStart rebuilt majority of framework from Beta 1 to Beta 2
- Also powers Analog (full-stack Angular framework by Brandon Roberts)
- Vinxi = JavaScript server toolkit for building full-stack apps/frameworks
- Inspired by Bun's app bundler
Code Reduction and Maintainability
- SolidStart went from 10,000 lines of code → 1,400 lines
- File count reduced from 150 → 32 files
- 10x easier to work in codebase
- Massive win for development velocity and maintenance overhead
New Deployment and Configuration Features
- Full access to Nitro's settings and plugin architecture
- Open standard with own ecosystem
- Pre-rendering support including automated link crawling
- Dozens of built-in deployment presets
- Full power of H3 universal HTTP server
- Integration with Node.js ecosystem
Router Architecture Changes
- Router now agnostic/separate package instead of deeply integrated
- Router can iterate independently from framework
- Other routers can be introduced
- File system routing consumable by any router
- Route config support via exported config objects
- Contrasts with React's approach of tighter router-framework integration
Server Functions - "use server" Implementation
- Moved from "server$" convention to React's "use server" directive
- Key differences from React implementation:
- Cannot inline server functions like React server components
- Must bind values instead of automatic closure inference
- Server functions are just functions (not actions)
- Actions = router concern, server functions = server execution
- RPC in browser, plain function calls on server
- No closure extraction - only module scope variables
- No automatic server code serialization
- Works with existing promise libraries (create resource, TanStack Query)
- Uses solid-serializer (serol) for encoding/streaming various data formats
- Supports streaming promises and async iterators
Client-Side Application Support
- Serious commitment to supporting SPAs and client-rendered apps
- Toggle SSR false in config for client-only mode
- Client-only apps can still use server functions
- "client only" wrapper for code that can't run on server
- Lazily loaded after hydration (similar to Next.js dynamic imports with SSR: false)
Additional Features and Libraries
- SolidRouter: async cache and action functionality
- create route data and create server data APIs
- Better TypeScript support
- Meta library: zero-config SSR head injection
- Backward compatibility with old SolidRouter version
- File system routing, advanced bundling, universal server runtime
Release Status and Future
- Still in beta, working toward 1.0
- Much happier path to 1.0 after foundation rebuild
- Remaining work: TypeScript improvements, testing, bug fixes, deployment bundling
- Ryan Carniato acknowledged long development time and apologized for delays
