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

@zenuinebit/invoice-number

v0.1.0

Published

Sequential invoice numbers with financial-year resets and GST-compliant format checks.

Downloads

172

Readme

@zenuinebit/invoice-number

Sequential invoice numbers that restart each financial year, plus a check for the Indian GST format rule. No dependencies. Dates are "YYYY-MM-DD" strings.

import { next, checkGstFormat, financialYear } from "@zenuinebit/invoice-number";

const format = { pattern: "INV/{FY}/{SEQ:4}" };       // reset defaults to "financial-year"

// First invoice: no counter yet
let r = next(null, "2025-04-01", format);              // { number: "INV/2025-26/0001", counter: { period: "2025-26", seq: 1 } }
r = next(r.counter, "2025-09-10", format);             // "INV/2025-26/0002"
r = next(r.counter, "2026-04-01", format);             // "INV/2026-27/0001" - new financial year

checkGstFormat("INV/2025-26/0042");                    // { valid: true, problems: [] }
financialYear("2025-03-31");                           // "2024-25"

Pattern tokens: {FY} 2025-26, {FY2} 2526, {YYYY}, {YY}, {MM}, {SEQ:n} (sequence padded to n digits) and {SEQ}. Reset: "financial-year" (default), "calendar-year", "month", "never". fyStartMonth defaults to 4 (April).

Use it safely

  • The package keeps no state. Store the counter in your database and call next inside the same transaction (or with a row lock) that saves the invoice. Two requests reading the same counter would otherwise issue the same number.
  • A back-dated invoice is fine inside the current period but refused if it falls in an earlier one, so it cannot reuse a number.
  • checkGstFormat tests Rule 46: at most 16 characters, only letters, digits, / and -. INV/2025-26/00042 is 17 characters and fails, so size your pattern for it.

Not included: credit-note or debit-note series, multiple series per branch (use one counter per series), and gap detection.