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

ssrer

v0.2.0

Published

Server-Side Rendering with a headless browser.

Downloads

7

Readme

ssrer

Overview

ssrer is an abbreviation for Server-Side Renderer. ssrer sends a request with a headless browser called Puppeteer. Since it uses headless browser the requests from it can be treated just the same as requests from real users.

ssrer shows more power with ssrer-express-middleware in Node.js and Express environment.

How to Use

$ git clone [email protected]:cam-inc/ssrer.git
$ npm install .
$ PORT=3000 npm run start

http://localhost:3000/?url=https://google.com/ to get string fo HTML context.

Queries

| name | required | default | description | | ---- | -------- | ------- | ----------- | | url | yes | - | URI-encoded url of a website to scrape. | | width | no | 1024 | width of viewport. | | height | no | 768 | height of viewport. | | timeout | no | 10000 | time in milliseconds to timeout. | | waitUntil | no | networkidle | networkidle or load can be passed. with networkidle, the page will be considered loaded when the network activity stays idle for a while. with load, the page will be considered loaded when HTML's load event is fired. | | cache | no | true | if false then ssrer doesn't use cache store. | | disableRequests | no | false | if true then all requests other than type of Document will be aborted. |

with Dockerfile

as an example.

$ docker build -t ssrer ./
$ docker run -it -p 3000:3000 ssrer
$ curl http://localhost:3000/\?url=https://google.com/

How to Develop

$ docker run -it -p 3000:3000 -v /host/path/to/ssrer/:/docker/ssrer/ ssrer npm run watch