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

opscms-ecommerce-plugin

v1.11.0

Published

Storefront commerce for an OpsCMS platform: catalogue, cart, orders, customers, discounts, checkout and payments settlement, with customer retention.

Readme

opscms-ecommerce-plugin

Storefront commerce for an OpsCMS platform, built with opscms-sdk: what a shop needs behind its storefront.

  • Customers with sign-in (register, verify email, forgot and reset password, update), catalogue (catalogue-categories, catalogue-items), orders, promotions, discounts and their reservations (redeem, release, commit), saved carts and cart events.
  • Payments settlement. The order, the ledger (payment-transactions), the payment endpoints (/api/payments/*) and the settlement live here; a payment plugin (Paystack, Monnify, OPay, …) only says how to talk to its service and keeps its own keys in its own table. Install at least one.
  • Customer retention and consent: five events (Welcome, Cart, Checkout, Win-back, Post-purchase), each on or off per shop; nothing is sent to a customer who has not agreed, and every message carries a link to stop them (POST /api/marketing-consent).
  • Jobs: abandoned-cart recovery, post-delivery review requests, payment reconciliation and the retention sweep.

Social Login extends customers, so it is registered after this plugin.

Install

From the admin: Plugins → Install from npm → opscms-ecommerce-plugin. The platform creates the plugin's tables (its one migration), lists the plugin with its logo, and restarts to start it. Removing the plugin drops its tables and everything in them: customers, orders, the catalogue. The admin asks which to do.

The platform currently carries this plugin in its own code under the same key; install the package only after that copy has been removed.

Needs

payload ^3 and opscms-sdk ^0.1.9 (the platform provides both). bcryptjs is its own dependency.

Tests

tests/ holds them. They run against a stand-in for the platform (tests/support/fakePlatform.ts) and an in-memory Payload, so no database is needed:

npm install
npm run typecheck && npm test && npm run build && npm pack --dry-run