daopk / fastify-nextjs

React server side rendering support for Fastify with Next

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

fastify-nextjs

js-standard-style CI workflow

React server side rendering support for Fastify with Next Framework.

Install

npm i fastify-nextjs next --save

Usage

Since Next needs some time to be ready on the first launch, you must declare your routes inside the after callback, after you registered the plugin.
The plugin will expose the api next in Fastify that will handle the rendering for you.

const fastify = require('fastify')()

fastify
  .register(require('fastify-nextjs'))
  .after(() => {
    fastify.next('/hello')
  })

fastify.listen(3000, err => {
  if (err) throw err
  console.log('Server listenging on http://localhost:3000')
})

All you server rendered pages must be saved in the folder pages, as you can see in the next documentation.

// /pages/hello.js
export default () => <div>hello world</div>

If you need to pass custom options to next just pass them to register as second parameter.

fastify.register(require('fastify-nextjs'), { dev: true })

If you need to handle yourself the render part, just pass a callback to next:

fastify.next('/hello', (app, req, reply) => {
  // your code
  // `app` is the Next instance
  app.render(req.raw, reply.raw, '/hello', req.query, {})
})

Acknowledgements

This project is kindly sponsored by:

License

Licensed under MIT.

About

React server side rendering support for Fastify with Next

License:MIT License


Languages

Language:JavaScript 95.6%Language:TypeScript 4.4%