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

@feedkit/feedback-react

v0.1.4

Published

React bindings for @feedkit/feedback-core: <FeedbackProvider> and the useFeedback() hook.

Readme

@feedkit/feedback-react

React bindings for @feedkit/feedback-core: a <FeedbackProvider> and the useFeedback() hook. The widget renders in a Shadow DOM (no CSS leaks) and captures technical context automatically — console, network, rrweb session replay, screenshot and environment. Pair it with @feedkit/feedback-supabase to persist with no backend of your own.

Works with React 17, 18 and 19 — including StrictMode.

Install

npm i @feedkit/feedback-core @feedkit/feedback-react @feedkit/feedback-supabase

Setup

Define the config outside the component (the provider reads it once), then wrap your app:

import { FeedbackProvider } from '@feedkit/feedback-react';
import { supabaseTransport } from '@feedkit/feedback-supabase';
import type { FeedbackConfig } from '@feedkit/feedback-core';

const feedbackConfig: FeedbackConfig = {
  transport: supabaseTransport({
    url: import.meta.env.VITE_SUPABASE_URL,
    anonKey: import.meta.env.VITE_SUPABASE_ANON_KEY,
  }),
  ui: { position: 'right', theme: 'auto', locale: 'pt-BR' },
};

createRoot(document.getElementById('root')!).render(
  <FeedbackProvider config={feedbackConfig}>
    <App />
  </FeedbackProvider>,
);

The floating launcher mounts automatically. That's it.

useFeedback()

import { useFeedback } from '@feedkit/feedback-react';

function Header({ user }) {
  const feedback = useFeedback();

  return (
    <>
      <button onClick={() => feedback.open('bug')}>Report a bug</button>
      <button onClick={() => feedback.identify({ id: user.id, name: user.name, email: user.email })}>
        after login
      </button>
      <button onClick={() => feedback.reset()}>on logout</button>
    </>
  );
}

| Method | What it does | |---|---| | open(type?) | Opens the widget, optionally straight into 'idea' \| 'comment' \| 'bug' | | close() | Closes the panel | | identify(user) | Attaches the logged-in user to every payload | | reset() | Clears identification (the persistent anonymousId stays) | | setConsent(enabled) | Opt-out: stops captures and clears buffers | | setMetadata(obj) | Custom key/values attached to every payload | | submit(type, message, opts?) | Sends programmatically, without opening the widget |

Calling useFeedback() outside the provider throws a descriptive error.

Notes

  • SSR safe: the client is constructed without touching the DOM; the widget only mounts in the browser.
  • StrictMode safe: the double mount/unmount in React 18+ dev mode leaves exactly one working widget.
  • rrweb, html2canvas and pako are lazy-loaded via dynamic import — out of your first load.

See @feedkit/feedback-core for what gets captured, privacy controls and the full config reference.

MIT © Eduardo Santana