5629223407
[With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples need to be updated, so the following snippet updated all the examples to a compatible react version. ```bash cd examples/ fd -g 'package.json' | xargs sed -r -i 's/"react": ".*"/"react": "^17.0.2"/ fd -g 'package.json' | xargs sed -r -i 's/"react-dom": ".*"/"react-dom": "^17.0.2"/' # exclude experimental react version git checkout with-reason-relay/package.json ``` |
||
|---|---|---|
| .. | ||
| pages | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
| server.js | ||
Custom Koa Server example
Most of the time the default Next.js server will be enough but there are times you'll want to run your own server to integrate into an existing application. Next.js provides a custom server api.
Because the Next.js server is a Node.js module you can combine it with any other part of the Node.js ecosystem. In this case we are using Koa.
Preview
Preview the example live on StackBlitz:
How to use
Execute create-next-app with npm or Yarn 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
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()))