terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity
next.js/examples/custom-server
History
Tim Neutkens 59281adef3 Allow parsed url to be passed down (#950) 
* Allow parsed url to be passed down

* Update example to reflect url passing

* Check if passed url.query is empty

* Rename url to parsedUrl
2017-02-02 12:21:08 +05:30
..
pages Programmatic API (#310) 2016-12-16 12:33:08 -08:00
package.json set build and start npm scripts on all examples (#549) 2016-12-28 10:12:24 -08:00
README.md Fix link (#789) 2017-01-16 18:23:24 -03:00
server.js Allow parsed url to be passed down (#950) 2017-02-02 12:21:08 +05:30

README.md

Custom server example

How to use

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/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.