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

fillfeedback-reviews

v1.0.4

Published

A modern, performant React component for displaying FillFeedback reviews with lazy loading and infinite scroll

Readme

fillfeedback-reviews

Internal NPM package — React component for embedding FillFeedback reviews with horizontal scroll, lazy loading, and infinite scroll.

CSS is auto-injected at runtime. No CSS import needed anywhere — ever.


Install

npm install fillfeedback-reviews

Usage

import { FillFeedbackReviews } from "fillfeedback-reviews";
// ← no CSS import. Done.

export default function Page() {
  return (
    <FillFeedbackReviews
      apiKey="your-api-key"
      theme="auto"
      minRating={4}
      maxReviews={20}
      initialLoadCount={6}
      onReviewClick={(review) => console.log(review)}
    />
  );
}

Props

| Prop | Type | Default | Description | | ------------------ | ----------------------------- | ------------ | ---------------------------------------- | | apiKey | string | required | FillFeedback API key | | formId | string | undefined | Filter by form ID | | theme | 'light' \| 'dark' \| 'auto' | 'auto' | Color theme | | showRating | boolean | true | Show star rating | | showDate | boolean | true | Show review date | | showAvatar | boolean | true | Show avatar / initials | | showVideos | boolean | true | Show video attachments | | showDocuments | boolean | false | Show document links | | maxReviews | number | 50 | Max reviews to fetch | | minRating | number | 1 | Min star filter (1–5) | | initialLoadCount | number | 6 | Reviews shown initially | | className | string | undefined | Extra class on wrapper for CSS overrides | | onReviewClick | (review: Review) => void | undefined | Card click callback |


Custom Styling

Override CSS variables on .fv-wrapper:

.fv-wrapper {
  --fv-primary: #3b82f6;
  --fv-border-radius: 20px;
  --fv-spacing: 24px;
  --fv-star-filled: #facc15;
  --fv-bg-dark: #0f172a;
}

Scope per-instance with the className prop:

<FillFeedbackReviews apiKey="..." className="my-reviews" />
.my-reviews {
  --fv-primary: #ef4444;
}

Full variable list: src/styles/index.css.


How CSS injection works

Styles live as a minified string in src/styles/inject.ts. On first import, the module creates a <style id="__fv_styles__"> tag in document.head. The id check makes it idempotent — multiple instances don't duplicate the tag.

Updating styles

  1. Edit src/styles/index.css
  2. Run:
    npx postcss src/styles/index.css -o /tmp/styles.min.css --use cssnano
  3. Copy the output of /tmp/styles.min.css and paste it as the css string in src/styles/inject.ts
  4. Rebuild: npm run build

Dev workflow

npm install        # install deps
npm run build      # compile → dist/
npm run dev        # watch mode
npm run clean      # delete dist/

Publishing

# 1. Edit src/ as needed
# 2. If CSS changed, follow "Updating styles" above
# 3. Bump version in package.json
# 4. Build
npm run build
# 5. Publish
npm login          # first time only
npm publish