Puppeteer(Chrome headless node API) based web page renderer

Puppeteer (Chrome headless node API) based web page renderer.

Useful server side rendering through proxy. Outputs HTML, PDF and screenshots as PNG.

Requirements

You can run Chromium or docker.

Getting Started

Start server using docker (If you can not run Chromium and installed docker)

docker run -d --name renderer -p 8080:3000 zenato/puppeteer-renderer

Local (git clone)

npm install

Start server (If you can run Chromium)

npm start

(service port: 3000)

Locally build the image

docker build -t local/puppeteer-renderer .
docker run -d --name renderer -p 8080:3000 local/puppeteer-renderer

Test on your browser

Input url http://localhost:{port}/?url=https://www.google.com

If you can see html code, server works fine.

Puppeteer customization

When starting npm start or docker container you can customize puppeteer using environment variables.

• IGNORE_HTTPS_ERRORS=true - Ignores HTTPS errors
• PUPPETEER_ARGS='--host-rules=MAP localhost yourproxy' - Ads additional args that will be passed to puppeteer. Supports multiple arguments.

Integration with existing service.

If you have active service, set proxy configuration with middleware. See puppeteer-renderer-middleware for express.

const renderer = require('puppeteer-renderer-middleware');

const app = express();

app.use(renderer({
  url: 'http://installed-your-puppeteer-renderer-url',
  // userAgentPattern: /My-Custom-Agent/i,
  // excludeUrlPattern: /*.html$/i
  // timeout: 30 * 1000,
}));

// your service logics..

app.listen(8080);

API

PDF File Name Convention

Generated PDFs are returned with a Content-disposition header requesting the browser to download the file instead of showing it. The file name is generated from the URL rendered:

License

MIT

Copyright (c) 2017-present, Yeongjin Lee