@haatlabs-core/nest-billing

中文文档
0.18.5发布于 2026/11/14Apache-2.0TypeScriptESM + CJS近 30 天下载 4755

NestJS billing: plans, periods, metered usage, plan assignment and payment events applied once.

原始使用文档

@haatlabs-core/nest-billing

The billing every app shares: the plan in force and its period, usage counted once per key under a per-organization lock, plan assignment and seeding, gateway prices, payment events applied once and in order, and feature switches. An app passes its own tables (built from @haatlabs-core/db-core's billing column sets) and its catalog: what it counts, what it caps, and what a plan may leave out.

stores (optional): the app's stores, for Shopify billing (charging a store through Shopify). A web app leaves it out, and the module then has no Shopify billing routes or service.

Who may change the plan: buying, changing and cancelling it (POST billing/checkout, billing/cancel, and Shopify billing's checkout, confirm and cancel) is the whole organization's. The staff of one store in an organization made on the dashboard (a store-only principal, me.storeOnly) are refused with 403 FORBIDDEN and PLAN_CHANGES_MESSAGE ("Plan changes are made by the account's owner"); they still read GET usage and GET plans. An app's plan page hides its buttons from them.

Test charges: a Shopify charge is a test charge when SHOPIFY_BILLING_TEST is true or the shop is a partner development store, which Shopify is asked with the store's own token at checkout (shop { plan { partnerDevelopment } }); a real store gets a real charge. A development store's approved test charge puts it on the plan. When Shopify does not answer that question, nothing is charged or changed: the request fails with a transient 503.

shopifyThrottle (optional): the app's RedisShopifyThrottle, so Shopify billing paces each shop with the app's own jobs; without it, the process throttle. billingThrottleMaxWaitMs (default 10 s) is the longest a billing call waits there for its turn, not the throttle's minute, since a merchant is waiting on the page; it then goes.

Install

pnpm add @haatlabs-core/nest-billing

It leaves these packages to your app, so the app holds one copy: @nestjs/common, @nestjs/core, drizzle-orm, fastify, reflect-metadata, rxjs, zod.

版本与发布记录

@haatlabs-core/nest-billing 共发布 27 个版本,首次发布于 2026/10/23;过去 12 个月发布了 27 个版本。

版本发布日期距今
0.18.5latest2026/11/144 天前
0.18.42026/11/134 天前
0.18.32026/11/134 天前
0.18.22026/11/134 天前
0.18.12026/11/134 天前
0.18.02026/11/134 天前

关于 @haatlabs-core/nest-billing 的常见问题

@haatlabs-core/nest-billing 是什么?

NestJS billing: plans, periods, metered usage, plan assignment and payment events applied once.

如何安装 @haatlabs-core/nest-billing?

在项目目录运行 npm install @haatlabs-core/nest-billing,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:zod(^4.6.5)、rxjs(^7.8.2)、fastify(^5.12.5)、drizzle-orm(^0.45.3)、@nestjs/core(^12.1.2)、@nestjs/common(^12.1.2)、reflect-metadata(^0.2.2)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@haatlabs-core/nest-billing 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@haatlabs-core/nest-billing 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@haatlabs-core/nest-billing 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=24。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@haatlabs-core/nest-billing 可以商用吗?

@haatlabs-core/nest-billing 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@haatlabs-core/nest-billing 的下载量有多少?

根据 npm 官方下载统计,@haatlabs-core/nest-billing 在 2026/10/17 – 2026/11/15 这 30 天内被下载 4,755 次,日均约 159 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@haatlabs-core/nest-billing 还在维护吗?

最新版本 0.18.5 发布于 2026/11/14(4 天前);至今共发布 27 个版本,其中过去 12 个月发布了 27 个;首次发布于 2026/10/23。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。