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

@wsh4and/utils

v1.1.4

Published

Revamp all

Readme

A collection of simple utilities

Revamp all

version: 1.1.4

  • Fix Supabase env when used in NextJs
    • NextJs requires you to expose the variables to public with a prefix like this
    NEXT_PUBLIC_YOUR_VAR;
    so you need to define that in your local env
    • Make sure you name them correctly in order to use the utils usePostSupabase like this
    NEXT_PUBLIC_SUPABASE_URL; // for your URL Supabase
    NEXT_PUBLIC_SUPABASE_ANON_KEY; // for your ANON KEY
    • If you want to name them differently, use it like this and just make sure that your env vars are not undefined
    const PARAMS: ISupabase = {
      // Schema public sudah default, tidak perlu define
      db: {
        table: 'brand',
        select: '*',
        // select: 'item_code, item_name',
        page: 1,
        pageSize: 5,
      },
      client: {
        supabaseUrl: process.env.YOUR_SUPABASE_URL,
        supabaseKey: process.env.YOUR_SUPABASE_ANON_KEY,
      },
    };

version: 1.1.0

- Supabase
  - Required supabase key
  - Auth (Login, Logout) (not done yet)
  - Test getting data when RLS enable (not done yet)
  - Using custom hooks based on supabase

version: 0.0.1

- add row number function
- simple fetcher with axios