mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

History

Juan Olvera 7e12997af6 Test updater script on examples folder (#5993 ) I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder.		2019-01-05 12:19:27 +01:00
..
pages	Add prettier for examples directory (#5909 )	2018-12-17 17:34:32 +01:00
package.json	Test updater script on examples folder (#5993 )	2019-01-05 12:19:27 +01:00
README.md	#4751 - Explicitly mention install when cloning examples (#4758 )	2018-07-11 23:56:15 +02:00
server.js	Add prettier for examples directory (#5909 )	2018-12-17 17:34:32 +01:00

README.md

Example app where it caches SSR'ed pages in the memory

How to use

Using `create-next-app`

Execute create-next-app with Yarn or npx to bootstrap the example:

npx create-next-app --example ssr-caching ssr-caching-app
# or
yarn create next-app --example ssr-caching ssr-caching-app

Download manually

Download the example:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/ssr-caching
cd ssr-caching

Install it and run:

npm install
npm run dev
# or
yarn
yarn dev

Deploy it to the cloud with now (download)

now

The idea behind the example

React Server Side rendering is very costly and takes a lot of server's CPU power for that. One of the best solutions for this problem is cache already rendered pages. That's what this example demonstrate.

This app uses Next's custom server and routing mode. It also uses express to handle routing and page serving.