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

invoice-and-dispute

v1.1.7

Published

Reusable React invoice and dispute flow, exported as the InvoiceAndDisputePage component

Readme

Invoice and Dispute Library

A reusable React invoice and dispute flow component library with a local playground app for previewing the UI.

Requirements

  • Node.js 18+ (or compatible LTS)
  • npm 10+ (or yarn/pnpm if preferred)

Install dependencies

npm install

Run the local playground app

The project ships with a playground app under playground/.

npm run dev

Then open the local URL printed by Vite, usually:

http://localhost:5173

Preview the production build locally

npm run build
npm run preview

Then open the preview URL printed by Vite.

Configuration (runtime props)

Consumers configure the backends and Stripe key at runtime by passing a config prop to InvoiceAndDisputePage — no rebuild required per environment:

import { InvoiceAndDisputePage } from "invoice-and-dispute";

<InvoiceAndDisputePage
  config={{
    enforcementBaseUrl: "https://compliance.staging.premiumparking.com",
    complianceBaseUrl: "https://compliance.staging.premiumparking.com",
    paymentsBaseUrl: "https://compliance.staging.premiumparking.com",
    stripePublishableKey: "pk_test_xxx",
    source: "glideparcs",
    mpsBaseUrl: "https://premiumneworleans.mpspark.com", // optional; MPS invoices pay in-app as Premium
    disputeMaxFileMb: 10,
  }}
/>;

Point enforcementBaseUrl at glideparcs-enforcement.

  • Invoice lookup and dispute use existing /v1/admiral APIs (/violations.json, /violations/citations.json, /customer_appeal_forms.json).
  • TextPay snapshot and SPA card pay use /enforcement-web (/textpay_payments, /payment_intents, /payments).

paymentsBaseUrl is only a fallback for the same /enforcement-web payment host.

All keys are optional. Resolution precedence for each value is:

  1. The config prop above.
  2. A build-time VITE_* env var (see .env.example) — mainly for the playground.
  3. The Vite dev-proxy path (/pp-enforcement, /pp-compliance, /pp-payments), which only works while running npm run dev.

Package contents

  • src/ – library source code
  • playground/ – local demo app for the component library
  • dist/ – build output after running npm run build
  • scripts/ – build utilities (for example scripts/scope-css.mjs)

Available npm scripts

  • npm run dev / npm run playground - start the Vite development server using playground/vite.config.js
  • npm run build - build the library and run the CSS scoping script
  • npm run preview - preview the built playground app locally
  • npm test - run payment/MPS client contract tests