History

Sebastian Markbåge 0a76fb9ec4 Copy from build to node_modules instead of linking to builds (#26210 ) Using the `link:` protocol to create a dependency doesn't work when we edit the `package.json` to lock the version to a specific version. It didn't really work before neither, it was just that `yarn` installed an existing `scheduler` dependency from npm instead of using the built one. So I'm updating all the fixture to use the technique where we copy files instead.		2023-02-21 14:48:37 -05:00
..
public	SSR fixture (#9547 )	2017-04-27 21:03:32 -07:00
server	Upgrade prettier (#26081 )	2023-01-31 08:25:05 -05:00
src	Fix fixture	2022-03-25 17:38:10 +00:00
README.md	Use Yarn Workspaces (#11252 )	2017-10-19 00:22:21 +01:00
package.json	Copy from build to node_modules instead of linking to builds (#26210 )	2023-02-21 14:48:37 -05:00
yarn.lock	Copy from build to node_modules instead of linking to builds (#26210 )	2023-02-21 14:48:37 -05:00

README.md

SSR Fixtures

A set of test cases for quickly identifying issues with server-side rendering.

Setup

To reference a local build of React, first run npm run build at the root of the React project. Then:

cd fixtures/ssr
yarn
yarn start

The start command runs a webpack dev server and a server-side rendering server in development mode with hot reloading.

Note: whenever you make changes to React and rebuild it, you need to re-run yarn in this folder:

yarn

If you want to try the production mode instead run:

yarn start:prod

This will pre-build all static resources and then start a server-side rendering HTTP server that hosts the React app and service the static resources (without hot reloading).