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

estimated-read-time

v1.2.0

Published

Estimate the time taken to read a content

Downloads

99

Readme

estimated-read-time

NPM Github Downloads License

estimated-read-time helps to estimate the time taken to read a content.

Features

  1. Estimates the time taken to read any plain text content.
  2. Reduces the avg. reading WPM for a technical document based on its difficulty level.
  3. Calculate avg. WPM from previous total words and seconds. (Tip #1)

Installation

npm install estimated-read-time --save

Usage

var readtime = require('estimated-read-time');

var result = readtime.text(content);
//Returns
//{
//  word_count: 265
//  seconds: 60
//}

API

text(content, options)

  • content: the text to analyze
  • options.MIN_WORD_LEN: Avg Length of one word which will be used to count the no. of words in the content. (Default: 4)
  • options.WPM: Words Per Minute a person can read. (Default: 265)
  • options.IS_TECHNICAL_DOC: true or false indicating whether the content is a technical document. (Default: false)
  • options.TECH_DIFFICULTY: The Technical Difficulty of the content. Allowed values are 0 to 5. (Default: 3)
  • options.TOTAL_WORDS: Total Words read (Default: 0)
  • options.TOTAL_SECONDS: Total Seconds taken to read options.TOTAL_WORDS. (Default: 0)

Note: The WPM calculated using options.TOTAL_WORDS and options.TOTAL_SECONDS takes higher precedence than options.WPM.

Tips

  1. If you want to show the estimated reading time differently for each user based on their previous reading, then you can store the total words read by the user and the total seconds taken to read and pass them in options.TOTAL_WORDS and options.TOTAL_SECONDS.