Socket
Socket
Sign inDemoInstall

underpainting

Package Overview
Dependencies
6
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    underpainting

Render HTML on the server that's supposed to be rendered on the client


Version published
Maintainers
1
Created

Readme

Source

underpainting

Render HTML on the server that's supposed to be rendered on the client.

Why

From what I can tell it's still not possible to get decent search results for applications rendered entirely on the client. Google's fetch & render in webmaster tools seems to run JavaScript perfectly well, but the crawler itself must not be doing the same thing. Please correct me if I'm mistaken and / or just doing it rong!

Prerender is a nice idea for solving the problem, but it seems overly complex and ran my server OOM so I hacked this up instead.

How

BYO Chromium, talk to it using the remote debugging protocol. Optionally pass a custom "ready check" expression - defaults to document.querySelector('title').textContent. You can pass it in the querystring, base64 encoded under the key _ready_check_.

Example

$ node index.js &
$ curl http://unicodes.jessetane.com                       # empty dom
$ curl http://localhost:8080/http://unicodes.jessetane.com # dom with stuff

Configuration

Enviroment variables you can set. Sane (hopefully) defaults are provided but you will probably need to adjust them.

CHROME_{HOST,PORT}

Defaults to localhost:9222.

MAX_WORKERS

You probably want to limit the number of tabs you have open at any given time depending on the resources you have available. Defaults to 5.

READY_CHECK_INTERVAL

The interval at which to execute the target's ready check. Defaults to 100ms.

TIMEOUT

The amount of time workers are allowed to spend processing a request is capped. Defaults to 5000ms.

Notes

Installing / running Chrome headlessly on Ubuntu
apt-get install xvfb chromium-browser
xvfb-run chromium-browser --remote-debugging-port=9222
Running Chrome (with debugging enabled) on OS X
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
Disabling image loading

To disable image loading, you need this setting in Chrome's config file:

{
  "profile": {
    "default_content_setting_values": {
      "images": 2
    }
  }
}
  • the config file on linux:
    • ~/.config/chromium/Local\ State
  • the config file on mac:
    • ~/Library/Application\ Support/Google/Chrome/Default/Preferences

License

Public domain

FAQs

Last updated on 02 Mar 2016

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc