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 🙏

© 2024 – Pkg Stats / Ryan Hefner

prenderer

v1.1.2

Published

Prerender your JS pages in Chrome.

Downloads

12

Readme

prenderer

Prerender your JS pages in Chrome.

github

npm

Getting Started

Daemon

Installing Chrome

Getting Started

This module allows for server side rendering in chrome, meaning you can run it as a system user, say under apache or nginx.

It runs a headless instance of chrome to prerender the pages. You can either wait on a timeout for rendering to complete, or throw an event on the page to signal that Prenderer should snapshot the document and move on.

It has only been tested on Debian Linux.

Install:

$ npm i -g prenderer

Usage:

Supply a url and a timeout in milliseconds.

$ prenderer http://google.com --timeout=200

Remove the noise:

$ prenderer http://google.com --timeout=200 2>/dev/null

You also can omit the timeout, and throw a "renderComplete" event in your page's JS:

document.dispatchEvent(new Event('renderComplete'));
$ prenderer http://yourwebsite.com

During prerendering, the "prerenderer" cookie will be set. You can use this to detect prerendering in your page js.

Daemon

Use the following command to run Prenderer in daemon mode. If no port number is supplied, 3003 will be used.

$ prenderer --daemon 3003

Use URLS like the following to prerender over the network:

http://localhost:3003/?url=http://yahoo.com

Streaming

Run Prenderer in streaming mode with the following command:

$ prenderer --streaming

In this mode, Prenderer will load URLs from STDIN, separated by newlines.

Results will also be one line each, as newlines are escaped.

Installing Chrome

If you're in a pure CLI environment, like in SSH or Docker, you can't exactly go to google.com/chrome and click download (actually you can with lynx, but I digress).

Add Google's key to Apt:

$ wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -

Add the repo to your sources & update apt:

$ echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' | tee /etc/apt/sources.list.d/google-chrome.list

$ apt-get update

Install Chrome

$ apt install google-chrome-stable

Install Prenderer:

$ npm i -g prenderer

Thats it, now prenderer is ready to use.

Go crazy.