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

short-winded

v1.0.0

Published

Summarizes text

Downloads

1

Readme

Attempts to summarize text

#+BEGIN_SRC shell :results verbatim :exports both node example.js #+END_SRC

#+RESULTS: : It creates a new Socket.io client, and upon receiving the file-change-event from the server, reloads the page. That solves the problem for the index.html page, but what about the rest of the HTML pages? Your browser will not have direct access to the files you are editing, so it will rely on a smart web-server that has access to your file system. The best choice will be the one that allows you to solve the "refresh" problem easiest.

  • Usage #+BEGIN_SRC javascript :results none import { summarize } from 'short-winded' const summary = summarize('...', 75); // approximate word count #+END_SRC