Scaling Up

Scale a Sprig app by separating route pages, reusable .sprig components, state modules, and optional add-ons. The demo uses src/app/routes/ for pages and colocates app-specific components outside that route directory. File routes are lazy-loaded, while shared runtime APIs come from the core package entry.

Build with npm run build, test with npm test, and type-check the published API declarations with the existing type-check scripts. Consider Sprig's current boundaries—client rendering, focused templates, and no built-in HTTP or DI layer—when deciding whether it fits a larger app.