npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

prerender-hapi

v1.0.0

Published

Hapi plugin for prerendering JavaScript-rendered pages for SEO via Prerender.io

Readme

prerender-hapi

Hapi plugin for Prerender.io. Intercepts requests from bots and crawlers and serves prerendered HTML, so your JavaScript-rendered app is fully indexable by search engines and social media scrapers.

Compatible with @hapi/hapi v21+ and Node.js 18+.

Installation

npm install prerender-hapi

Usage

const Hapi = require('@hapi/hapi');

const server = Hapi.server({ host: 'localhost', port: 3000 });

await server.register({
  plugin: require('prerender-hapi'),
  options: {
    token: 'YOUR_PRERENDER_TOKEN'
  }
});

The plugin registers an onRequest extension that transparently proxies bot requests to Prerender.io and returns the prerendered HTML. Regular browser requests are unaffected.

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | token | string | process.env.PRERENDER_TOKEN | Your Prerender.io token | | serviceUrl | string | process.env.PRERENDER_SERVICE_URL or https://service.prerender.io/ | Prerender service URL (use this for self-hosted Prerender) | | protocol | string | null | Force a protocol (http or https). Defaults to the server's protocol | | beforeRender | async function(request) | async () => null | Called before each prerender request. Return a cached response object { status, headers, body } to skip the Prerender.io call | | afterRender | async function(request, response) | async () => {} | Called after a successful prerender. Use this to cache the response. Can be sync or async |

Environment variables

PRERENDER_TOKEN=your_token_here
PRERENDER_SERVICE_URL=https://service.prerender.io/  # optional

Self-hosted Prerender

await server.register({
  plugin: require('prerender-hapi'),
  options: {
    serviceUrl: 'http://your-prerender-server:3000'
  }
});

Caching example

const cache = new Map();

await server.register({
  plugin: require('prerender-hapi'),
  options: {
    token: 'YOUR_PRERENDER_TOKEN',
    beforeRender: async (request) => {
      return cache.get(request.url.href) || null;
    },
    afterRender: (request, response) => {
      cache.set(request.url.href, response);
    }
  }
});

How it works

Requests are prerendered when all of the following are true:

  • The HTTP method is GET
  • The User-Agent matches a known bot/crawler (Googlebot, Bingbot, Twitterbot, GPTBot, ClaudeBot, etc.)
    — OR the URL contains _escaped_fragment_
    — OR the X-Bufferbot header is present
  • The URL does not end with a static asset extension (.js, .css, .png, .woff2, .webp, etc.) — matched case-insensitively

Everything else passes through to your normal route handlers.

License

MIT