npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




Collection of handy utility functions for working within a Next.js project.





npm NPM npm

Handy utilities for building React components that render as nice server-side as they do on the client.


Via npm

npm install --save next-utils

Via Yarn

yarn add next-utils

How to use

After building a few packages that all handled server-side requests, two common functions and classes emerged that were almost identical for them all, getDataFromTree and RenderPromises.

For examples of how these can be used, please reference the repos that are using these


Used to render a React tree server side and expose the renderPromises method via a Provider to allow for children to register themselves and resolve all requests initiated by child components.


Manages and resolves query instances that have registered themselves. Relies on all registered instances to have a public fetchData method exposed that is responsible registering with the context provided renderPromises example.

import React, { Component } from 'react';

class RequestComponent extends Component {
  constructor(props) {

    this.state = {
      data: null,
      error: null,
      loading: false,
      fetched: false,


  async fetchData() {
    return new Promise((resolve, reject) => {
      const {
      } = this.props;

      try {
        if (skip) {
          return resolve(null);

        const cacheKey = JSON.stringify(this.props);

        if (context.cache && context.cache.has(cacheKey)) {
          return resolve(;

        const request = fetch(url, options);

        if (context.cache && !context.renderPromises) {
          context.cache.write(cacheKey, request);

        const response = await request;

        if (context.renderPromises) {
          context.renderPromises.registerSSRObservable(this, response);

        return resolve(response);
      catch (error) {
        return rejectt(error);


  getQueryResult() {
    return this.state;

  render() {
    const {
    } = this.props;

    const finish = () => children(this.getQueryResult());

    if (context && context.renderPromises) {
      return context.renderPromises.addQueryPromise(this, finish);

    return finish();

Other Handy Utils

Because I got tired of repeating myself with these across multiple projects.

  • isClient - Basically just, typeof window !== 'undefined'
  • isServer - And, the inverse, typeof window === 'undefined'
import { useEffect } from 'react'
import { isServer } from 'next-utils'

useEffect(() => {
  if (isServer()) return client-side only stuff...

Used by


MIT © Ryan Hefner