maxjhandsome
/
react
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
react/fixtures/fizz
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 [Fizz] Pipeable Stream Perf (#24291) 2022-04-11 09:13:44 -07:00
scripts [Codemod] Update copyright header to Meta (#25315) 2022-10-18 11:19:24 -04:00
server Upgrade prettier (#26081) 2023-01-31 08:25:05 -05:00
src [Codemod] Update copyright header to Meta (#25315) 2022-10-18 11:19:24 -04:00
README.md Fix: Documentation typos (#24471) 2022-09-29 12:46:53 -04: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

Fizz Fixtures

A set of basic tests for Fizz primarily focused on baseline performance of legacy renderToString and streaming implementations.

Setup

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

cd fixtures/fizz
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).