Server-side Rendering of JavaScript in PHP
summary
Shows how to server-render React/Vue from PHP using webpack bundles and three practical runners: fork Node per request (simple but slow), embed V8 via v8js with snapshots (fast but hard to build), or run a long‑lived JS worker over a UNIX socket (fast and reusable). Demonstrates renderToString + hydration, using react-helmet for meta tags, Symfony/Twig integration, and libraries ReactRenderer ReactBundle phpexecjs; claims SEO and perceived-load wins (avoid 19s first paint on 3G; >50% abandon if >3s).
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:15Why server-side rendering
- 2:00History of web interactivity
- 4:21Dom manipulation challenges
- 6:30SEO and performance issues
- 9:20State-based frameworks
- 9:55React and component state
- 15:58Concept of SSR
- 16:25Hydration process
- 18:53PHP and SSR
- 22:42Node.js as a frontend API
- 23:57V8JS PHP extension
- 24:26V8JS snapshots and caching
- 25:46Alternative rendering servers
- 26:39Available PHP libraries
- 27:22Symfony bundle integration
- 27:38React on rails in PHP
- 27:48Managing global state
- 29:45Handling request context
- 30:28SEO meta tag management
- 32:26Sharing state with twig
- 33:07Browser specific code
- 33:20API calls on server
- 33:39Early testing advice
- 34:46Addressing frustration
- 35:22Summary
- 37:26Q&A
- 40:29Closing
related talks
01h 19mServer side rendering of React with Symfony
44mIntegrating React.js with PHP Projects
40mIntegrating React.js into a PHP application
46mRethinking Server-Side Rendering in Modern PHP Applications
24mServing content on the web: from PHP to RSC—and beyond
46mPushing the limits of PHP with React PHP
59mBring Your PHP Application to the Next Level with React.JS
33mRendering on the Web: Performance Implications of Application Architecture