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

naos

v1.0.7

Published

Dead simple command line monitoring and debugging tool, based on [Puppeteer](https://github.com/GoogleChrome/puppeteer).

Downloads

5

Readme

Naos ✨ ⛵️

Dead simple command line monitoring and debugging tool, based on Puppeteer.

Whats it do?

Specify an array of urls to scrape and naos will evaluate them through Puppeteer, returning you a status code and any browser console warnings or errors it finds.

Why?

Puppeteer is awesome and allows you to build very advanced integration test suites, however sometimes you don't need or don't have time to write anything more advanced than making sure your routes return a 200 and the console doesn't throw any errors. This can be very useful as a quick and basic regression checking tool.

Installation

npm install -g naos

Running

First create a config.json file like so:

{
  "protocol": "https",
  "host": "www.nytimes.com",
  "port": 443,

  "paths": [
    "/",
    "/section/world/"
  ]
}

And begin scraping:

naos --config ./config.json

With JSON output instead:

naos --config ./config.json --format json