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

evoly-invoice-lib

v4.2.8

Published

Components for invoicing shared between multiple projects - evoly-metering, and evoly-customer-portal.

Readme

Evoly Invoice Library

Components for invoicing shared between multiple projects - evoly-metering, and evoly-customer-portal.

Inframark workspace

Workspaces whose route starts with inframark, hc-mud-504, interstate-mud, or mayde-creek-mud render the Inframark statement style (src/app/invoice/inframark.tsx), a replica of the Starnik "Monthly Water Bill Statement" (models in src/app/assets/inframark/). No special wiring is needed: render <Invoice /> with workspaceRoute="inframark" (or any route with that prefix) and the usual props, and the dispatch in invoice-content.tsx does the rest.

import { Invoice } from "evoly-invoice-lib";

<Invoice
  workspaceRoute="inframark"
  pricingZone={pricingZone}   // zone name is printed as the district name
  from={from}
  to={to}
  oldIndex={oldIndex}
  newIndex={newIndex}
  lastPeriodIndex={lastPeriodIndex}
  address={address}
  factoryNumber={factoryNumber}
  clientNumber={clientNumber}
  medium={medium}
  multiplier={multiplier}
  categoriesQueryData={categories}
  conversionsQueryData={conversions}
  lng="en"
  // Optional, Inframark-specific enhancements:
  monthlyUsage={monthlyUsage}   // fills the 13-month usage chart
  customerCity={customerCity}   // city + ZIP line of the mailing block
/>

Data requirements on the evoly-metering side:

  • Units must have clientNumber set — the pricing-data endpoint (/api/client-number/pricing-data) looks units up by it and returns every unit sharing the number.
  • Each pricing zone needs billing categories/services priced in $ per 1000 gallons / per month (same as the other US workspaces).

Optional props (the invoice degrades gracefully without them):

  • monthlyUsage?: { month: Date; consumption: number }[] — up to 13 months of consumption history (display units, current period included). Without it the chart falls back to the two periods derivable from the indices.
  • customerCity?: string — e.g. "KATY, TX 77449"; printed under the street address in the mailing block, omitted when absent.

Known placeholders, until the corresponding data exists:

  • ACCOUNT NUMBER prints xxxxxx (real Inframark account numbers are not imported yet), ACCOUNT NAME prints Customer-Name, SECURITY CODE prints X-XXXXX-XXXX.
  • STATEMENT # is derived from the statement date (YYYYMMDD).
  • The remit-to address is Inframark corporate (17495 Village Green Drive, Jersey Village, TX) — confirm the real payment PO box with Inframark before production use (see the TODO on InframarkInfo).

Derived billing rules (from the Inframark sample statement): statement date = read-period end + 12 days, due date = end + 35 days, late penalty 15%.