Integration with ssr-caching about next-routes

[fridays]

I didn't try it yet, but it should work like this with the caching example:

const express = require('express')
const next = require('next')
const routes = require('./routes')
const dev = process.env.NODE_ENV !== 'production'
const app = next({ dir: '.', dev })
const handle = app.getRequestHandler()
const LRUCache = require('lru-cache')

const ssrCache = new LRUCache({
  max: 100,
  maxAge: 1000 * 60 * 60 // 1hour
})

app.prepare().then(() => {
  express().use(renderAndCache).listen(3000)
})

function renderAndCache (req, res) {
  if (ssrCache.has(req.url)) {
    return res.send(ssrCache.get(req.url))
  }

  // Match route + parse params
  const {route, params} = routes.match(req.url)
  if (!route) return handle(req, res)

  app.renderToHTML(req, res, route.page, params).then((html) => {
    ssrCache.set(req.url, html)
    res.send(html)
  })
  .catch((err) => {
    app.renderError(err, req, res, route.page, params)
  })
}

[sedubois]

Ah nice, will try 🙂 It might be helpful to document in README the routes.match() API.

[fridays]

I'll do that! Let me know if you encounter any issues. Closing this for now

[sedubois]

I tried in this branch: https://github.com/relatenow/relate/tree/ssr-caching

But I get in the server:

CACHE MISS: /__webpack_hmr
CACHE MISS: /_next-prefetcher.js
CACHE HIT: /__webpack_hmr

And in the console: EventSource's response has a MIME type ("text/html") that is not "text/event-stream". Aborting the connection.

The __webpack_hmr requests shouldn't hit the cache I guess, but don't know how to configure that using next-routes. Any help appreciated :)

[sedubois]

I tried adding this before checking the cache:

    if (req.url === '/__webpack_hmr') {
      return handle(req, res);
    }    

But still get

The script has an unsupported MIME type ('text/html').
Failed to load resource: net::ERR_INSECURE_RESPONSE

[sedubois]

I also think that somehow, the route('profile', '/:slug') shouldn't match on /__webpack_hmr. /__webpack_hmr shouldn't match on any user route.

[sedubois]

OK for some reason the console error doesn't appear any more (although I thought I had restarted the server to clear the cache).

The next issue is that it doesn't match on all the prefetcher routes, although this is the most important load that the server will get (most of the time, the server will only need to render when the user visits the home page, then the rest of SSR will only be triggered by the SSR requests):

Route not matched: /static/nprogress.css
Route not matched: /_next/-/commons.js
Route not matched: /_next/-/main.js
Route not matched: /_next/-/pages/
Route not matched: /_next/-/pages/discover
Route not matched: /_next/-/pages/about
Route not matched: /_next/-/pages/auth/login
Route not matched: /static/homepage/bg_TimMarshall.jpg

[sedubois]

I asked about this issue in the original PR: vercel/next.js#497 (comment)

[sedubois]

And I replied to myself 😄

Oh I keep forgetting, next-prefetcher doesn't do a pre-render, it just downloads the code.

[fridays]

route('profile', '/:slug') shouldn't match on /__webpack_hmr

It doesn't since the catchall update from the last version, can you check?

I just updated /_next/ to /_next in the ignored paths, so prefetcher urls won't be matched by catchall routes anymore too.

Also you can now use routes.isNextPath(req.url) to test against the list of ignored paths. Maybe that can be helpful when integrating with the caching system.

[sedubois]

It doesn't since the catchall update from the last version, can you check?

@fridays created #6

Also you can now use routes.isNextPath(req.url)

Seems to work 👍 (sedubois/relate@f8032ba#diff-bba6db1dd9623c6662b43cc660a5975cR20)