Branch: master
Find file History
#6151 Compare This branch is 7 commits behind canary.
vgrafe and timneutkens fixes a few inconsistencies in server routes (#6382)
I spotted a few typos in the server files, that might confuse new/unexperienced users. I hope I did catch them all!
Latest commit d7856c6 Feb 21, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
pages Add prettier for examples directory (#5909) Dec 17, 2018
README.md #4751 - Explicitly mention install when cloning examples (#4758) Jul 11, 2018
package.json Test updater script on examples folder (#5993) Jan 5, 2019
server.js

README.md

Deploy to now

Custom Koa Server example

How to use

Using create-next-app

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

npx create-next-app --example custom-server-koa custom-server-koa-app
# or
yarn create next-app --example custom-server-koa custom-server-koa-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/custom-server-koa
cd custom-server-koa

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

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.

Because the Next.js server is just a node.js module you can combine it with any other part of the node.js ecosystem. in this case we are using Koa to build a custom router on top of Next.

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.

Side note: Enabling gzip compression

The most common Koa middleware for handling the gzip compression is compress, but unfortunately it is currently not compatible with Next.
koa-compress handles the compression of the response body by checking res.body, which will be empty in the case of the routes handled by Next (because Next sends and ends the response by itself).

If you need to enable the gzip compression, the most simple way to do so is by wrapping the express-middleware compression with koa-connect:

const compression = require('compression');
const koaConnect = require('koa-connect');


server.use(koaConnect(compression()));