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

vt-feedback

v0.2.0

Published

Client SDK for submitting feedback to a VTHub instance, plus a themeable React feedback widget.

Readme

vt-feedback

Client SDK for submitting feedback to a self-hosted VTHub instance.

Install

npm install vt-feedback
# or
pnpm add vt-feedback

Setup

Every project points at the same VTHub instance, so set its URL once as an environment variable instead of passing it everywhere:

# .env.local
NEXT_PUBLIC_VTHUB_API_URL=https://vthub.yourdomain.com

apiUrl can still be passed explicitly (e.g. to point at localhost in dev, or override per-environment) — it takes priority over the environment variable when provided.

Framework-agnostic core

import { submitFeedback } from 'vt-feedback'

const result = await submitFeedback(
  { apiKey: process.env.NEXT_PUBLIC_VTHUB_API_KEY! },
  { category: 'bug', message: 'Saving fails on mobile Safari' },
)

React widget

import { FeedbackWidget } from 'vt-feedback/react'
import 'vt-feedback/react/styles.css'

export function App() {
  return (
    <FeedbackWidget
      apiKey={process.env.NEXT_PUBLIC_VTHUB_API_KEY!}
      theme={{ colorPrimary: '#7c3aed', radius: '10px' }}
    />
  )
}

apiKey is a per-project key created in the VTHub dashboard. It is safe to expose client-side — it only permits creating feedback submissions for that one project. Unlike apiUrl, it's not a good fit for a shared environment variable since it's different per project.

Build

npm run build