Provide way of forcing a 404

Let’s say you have a page file that matches the current route, but upon fetching some data in the addPageContext hook, you determine that necessary data is unavailable and the user should be served with a 404 error page. At present, I believe the only option available to a user here is to halt rendering of the page and render an error would be to throw an error within the addPageContext hook. However, this will end up as a 500, not a 404. In this specific case, we are deliberately throwing an error that we would like to be cast as a 404.

I have a suggestion for how this could be achieved - export error classes that can be imported and used to throw specific error types. E.g.

import { ServerError, NotFoundError } from 'vite-plugin-ssr';

export async function addPageContext({ url }) {

  const criticalData = await fetchCriticalData(url);

  if (!criticalData) {
    throw new NotFoundError;
  }
  return {
    criticalData
  }
}

[brillout]

What is your concrete use case?

You can already hack something like this today.

export async function render() {
  if (!criticalData) {
    return {dataMissing: true};
  }
}

// server.js

const renderPage = createPageRender(/*...*/)

app.get('*', async (req, res, next) => {
  const result = await renderPage({ url: req.url })
  if (result.dataMissing) {
    const result = await renderPage({ url: '/doesNotExist' })
    res.status(result.statusCode).send(result.renderResult)
    return;
  }
})

return render404Error(Page)

Yea I was thinking about something like this as well.

[brillout]

I still struggle to see a use case for this. But I’m happy to be shown wrong and more than happy to re-open this.