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

webpage-wc

v1.0.5

Published

Prints number of words in one or more webpages using the Readablity API

Downloads

5

Readme

webpage-wc

Prints number of words in one or more webpages using the Mercury Web Parser API

Installation

npm install -g webpage-wc

Usage

webpage-wc url1 url2 ... [--token <api_key>]

You only need to pass the API key on the first run. It will be saved to your configuration directory and automatically read on subsequent runs.

You can get your key at https://mercury.postlight.com/web-parser/.

Caveats

Although the Mercury Web Parser API reports the total word count in the parsed article, this number is not accurate as it includes the number of words in code blocks, webpage-wc does not include code blocks in the total word count, so only normal paragraphs are considered.