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

chromium-screenshot

v1.1.0

Published

Screenshot server using Chromium and Puppeteer

Downloads

4

Readme

Chromium Screenshot

Status

Codacy Badge Codacy Badge

Documentation

Package documentation is deployed to GitLab Pages.

Dependencies

This package requires Node.js 8.x or later; modules required by the package are documented in the package.json file.

Code Quality

To run the unit tests and generate a coverage report in /coverage with Mocha and Istanbul run npm install followed by npm test at the command line.

To run ESLint run npm install followed by npm run lint at the command line.

Generating documentation

Generating the docs requires Python to be installed, tested with v3.12. With the Python binary in the path, run, install MkDocs if not present:

➜  mkdir venv               
➜  python -m venv venv 
➜  source venv/bin/activate
➜  which python
/path/to/venv/bin/python
➜  python -V
Python 3.12.3
➜  pip install mkdocs mkdocs-material

Then to generate the docs run:

➜  npm i
➜  npm run docs

to generate static files in ./site.