Universal React applications are tough to configure. Either you buy into a framework like Next.js, fork a boilerplate, or set things up yourself. Aiming to fill this void, Razzle is a tool that abstracts all the complex configuration needed for SSR into a single dependency--giving you the developer experience of create-react-app, but then leaving the rest of your app's architectural decisions about frameworks, routing, and data fetching up to you. With this approach, Razzle not only works with React, but also Reason, Elm, Vue, Angular, and most importantly... whatever comes next.

CONTENTS

0:05 - Intro
0:13 - Jared’s open-source projects
1:10 - Introducing Razzle
2:00 - Static vs dynamic content
3:13 - Frameworks comparison: create-react-app, Gatsby, Next.js, Razzle
4:22 - Next.js features
4:53 - Next.js routing issues
6:19 - Razzle Demo
10:50 - Examples of Razzle integration with various frameworks
11:44 - Custom configuration
12:32 - Specify route config
13:53 - Server rendering caveats
14:34 - Migration from create-react-app
15:32 - Question: How easy is to implement SSR with Razzle for production app
18:16 - Question: Why is you SSR pain point?

RESOURCES

Razzle
https://github.com/jaredpalmer/razzle

Integration examples
https://github.com/jaredpalmer/razzle/tree/master/examples