History

Tim Neutkens ebf0c47c25 Upgrade standard.js (#4064 ) * Upgrade standard.js # Conflicts: # yarn.lock * Upgrade babel-eslint		2018-03-27 20:11:03 +02:00
..
pages	Programmatic API (#310 )	2016-12-16 12:33:08 -08:00
package.json	Upgrade React for all examples (#3113 )	2017-10-17 08:11:46 +02:00
README.md	Examples: use npx and yarn create to run create-next-app on examples (#4002 )	2018-03-14 09:09:46 +01:00
server.js	Upgrade standard.js (#4064 )	2018-03-27 20:11:03 +02:00

README.md

Custom server example

How to use

Using `create-next-app`

Download create-next-app to bootstrap the example:

npx create-next-app --example custom-server custom-server-app
# or
yarn create next-app --example custom-server custom-server-app

Download manually

Download the example or clone the repo:

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

Install it and run:

npm install
npm run dev

Deploy it to the cloud with now (download)

now

The idea behind the example

Most of the times the default Next server will be enough but sometimes you want to run your own server to customize routes or other kind of the app behavior. Next provides a Custom server and routing so you can customize as much as you want.

The example shows a server that serves the component living in pages/a.js when the route /b is requested and pages/b.js when the route /a is accessed. This is obviously a non-standard routing strategy. You can see how this custom routing is being made inside server.js.