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 🙏

© 2026 – Pkg Stats / Ryan Hefner

responsive-content.js

v2.0.1

Published

Transforms a piece of text at a breakpoint as well as produces a screen reader specific version.

Readme

responsive-content.js NPM version

Code climate

A JavaScript library that transforms a piece of text at a breakpoint as well as produces a screen reader specific version.

Why?

The specific use case this was created for was for the use of relative directions such as "left, right" to refer to the UI. With responsive design becoming so prevalent you need to be a little more careful when you use these as the element being referred to may not always be to the left.

Installing

Bower

# via bower
bower install --save responsive-content.js

# via npm
npm install --save responsive-content.js

Including

<script src="bower_components/responsive-content.js/src/responsive-content.js"></script>

Usage

This will change the span's content to "above" when the viewport is less than 600 pixels wide.

<span class="responsive-content" data-breakpoint="600" data-text="above">left</span>
<script>
  // Initialise
  responsiveContent();
</script>

Screen reader text

The optional data-accessible-text attribute can be used to specify a screen reader version of the text explicitly.

<span class="responsive-content" data-breakpoint="600" data-text="right" data-accessible-text="above">left</span>

This will transform to this, where the element with aria-hidden="true" will change depending on viewport width.

<span class="responsive-content" data-breakpoint="600" data-text="above">
  <span aria-hidden="true">to the left</span>
  <span style="position: absolute; left: -9999px;">above</span>
</span>