Opinionated tooling without the heavy scaffolding.

Typical flow

1. 1.  Author layouts + routes in app/pages/*.
2. 2.  Create interactive widgets in src/ using Vite.
3. 3.  Bind PHP data with useState() + useEffect().
4. 4.  Listen to route events via phpspa.on().
5. 5.  Deploy with pnpm build → manifest assets.

Integration

Use PhpSPA inside Laravel, Symfony, CodeIgniter, WordPress—or any custom framework.

• •  Mount controllers then swap views inside <div id="app">.
• •  Share auth context with Session or scoped hooks.
• •  Proxy API calls through PhpSPA Http\Request.

Deliverables

• •  pnpm dev launches Vite + PHP for hot reload.
• •  pnpm build emits versioned assets + manifest.
• •  app/layout/layout.php swaps dev/prod automatically.
• •  Debug hooks log transitions for profiling.

SEO & multi-page

PhpSPA renders every first request through PHP, so crawlers receive fully formed HTML, titles, and meta tags. Define multiple entry points by passing arrays to ->route([...]), scope per-route layouts with ->targetID(), and emit canonical titles via ->title(). Need a classic multi-page site? Simply add more components — each route can hydrate independently but still benefit from SPA navigations once the runtime boots.

• •  Static-first payloads keep SEO bots happy.
• •  Dynamic metadata comes from PHP before hydration.
• •  Array routes let one component serve multiple URLs.

Preloading & composition

Preload layout fragments or sibling apps so they are ready before PhpSPA swaps targets. Use ->name() to give each component a unique key, then chain ->preload('hero', 'sidebar') on the parent. PhpSPA runs those children on the server, caches their HTML, and hydrates them automatically when the main component renders.

return (new Component(fn () => '<Hero />'))
   ->name('landing')
   ->preload('hero', 'stats')
   ->route(['/landing', '/home'])
   ->targetID('main')

You can even preload entire micro-apps (dashboards, modals, counter demos) to avoid waterfalls when users land on a rich layout.

Native performance

The PhpSPA runtime streams responses through the FFIBridge so minification and compression are handled by a C++ extension instead of PHP string operations. Bundles are squeezed by the native compressor, then gzipped or brotlied before the request leaves the server, keeping the templating layer expressive while responses remain lean.

• •  Native tokenizer trims whitespace + comments in ~15ms for 300KB payloads.
• •  Streaming compressor emits pre-zipped HTML/JS so clients download 30–60% less.
• •  Fallbacks detect missing extensions and transparently switch to PHP compressors.