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 🙏

© 2025 – Pkg Stats / Ryan Hefner

readinglist-client

v0.2.4

Published

Client webapp for the Mozilla readinglist API.

Readme

Readinglist client

Build Status Dependency Status

This is work in progress at a temporary location.

Installation

Requires nodejs v0.10.29+ and npm v2.1.0+. To install the required dependencies:

$ npm install

This Web client also requires a running instance of the Readinglist server.

Configuration

You can configure the client using the following environment variables:

  • CLIENT_DEVICE_IDENTIFIER: The client identifier name; used when updating article read status (default: readinglist-client).
  • MAX_ITEMS_PER_PAGE: The maximum number of articles per result page; default: 10.
  • NODE_ENV: The nodejs environment name; default: production.
  • READINGLIST_SERVER_BASEURL: the Readinglist server base URL; default: http://0.0.0.0:8000/v0.
  • READABLE_PROXY_URL: the readable-proxy server base endpoint; default: http://0.0.0.0:3000/api/get.

Environment variables will be used during the build step to replace matching placeholders in resulting js assets. Eg. that means if you want to override the default API base url running the local development server, you can run:

$ READINGLIST_SERVER_BASEURL=http://my.alt.domain.tld npm start

Building & deploying

$ READINGLIST_SERVER_BASEURL="http://production.server.tld" \
  READABLE_PROXY_URL="https://readable-proxy.herokuapp.com/api/get" \
  npm run build

Result is then available in the build/ subfolder. This is what should be deployed to production.

Local dev server

$ npm start

Notes:

  • This local development server will watch for local asset changes and live-reload the page automatically;
  • It will set NODE_ENVto development;
  • The address used is http://localhost:4000.

Linting

$ npm run lint

Tests

This will run the unit test suite against a Karma browser matrix and exits.

$ npm test

TDD

This will launch a live Karma server watching and running tests on each source change.

$ npm run tdd