stripekit - npm Package Compare versions

Comparing version

0.1.1

0.2.0

+3

-2

package.json

		{
		"name": "stripekit",
		"version": "0.1.1",
		"version": "0.2.0",
		"description": "The create-next-app of Stripe. Declarative catalog reconciliation into your own Stripe account, plus correct-by-construction billing code you own.",
		"license": "MIT",
		"author": "Rafael Cammarano Guglielmi",
		"homepage": "https://rafaelcg.github.io/stripekit/",
		"homepage": "https://stripe.rafael.ltd/",
		"repository": {
		@@ -57,2 +57,3 @@ "type": "git",
		"@clack/prompts": "^0.7.0",
		"@modelcontextprotocol/sdk": "^1.0.0",
		"commander": "^12.1.0",
		@@ -59,0 +60,0 @@ "jiti": "^2.4.0",

+19

-8

README.md

		# stripekit

		[![npm](https://img.shields.io/npm/v/stripekit.svg)](https://www.npmjs.com/package/stripekit)
		[![CI](https://github.com/rafaelcg/stripekit/actions/workflows/ci.yml/badge.svg)](https://github.com/rafaelcg/stripekit/actions/workflows/ci.yml)
		[![license](https://img.shields.io/npm/l/stripekit.svg)](https://github.com/rafaelcg/stripekit/blob/main/LICENSE)
		[![docs](https://img.shields.io/badge/docs-stripe.rafael.ltd-635bff)](https://stripe.rafael.ltd/)

		The create-next-app of Stripe. Declare your product catalog in a config file, and `stripekit` reconciles your _own_ Stripe account to match it — creating and updating products, prices, the webhook endpoint, and the customer portal. No hosted service, no revenue share, no runtime dependency. Plain Stripe underneath, code you own on top.

		> Status: early. Ships `init`, `plan`, `push`, `pull`, and `dev` (local webhook forwarding). A `check` doctor is on the roadmap.
		> Status: early. Ships `init`, `plan`, `push`, `pull`, `dev` (local webhook forwarding), and `check` (a config/account doctor).

		@@ -44,9 +49,11 @@ ## Why

		\| Command \| What it does \|
		\| ---------------- \| ------------------------------------------------------------------------------------------------------------- \|
		\| `stripekit init` \| Scaffold `stripe.config.ts` and correct-by-construction billing code into a Next.js (App Router) app. \|
		\| `stripekit plan` \| Preview the changes `push` would make. Never mutates anything. \|
		\| `stripekit push` \| Reconcile your Stripe account to match `stripe.config.ts`. Test mode by default; live mode requires `--live`. \|
		\| `stripekit pull` \| Generate `stripe.config.ts` from your existing catalog (read-only). \|
		\| `stripekit dev` \| Forward Stripe webhooks to your local app and capture the signing secret (wraps `stripe listen`). \|
		\| Command \| What it does \|
		\| ----------------- \| ------------------------------------------------------------------------------------------------------------- \|
		\| `stripekit init` \| Scaffold `stripe.config.ts` and correct-by-construction billing code into a Next.js (App Router) app. \|
		\| `stripekit plan` \| Preview the changes `push` would make. Never mutates anything. \|
		\| `stripekit push` \| Reconcile your Stripe account to match `stripe.config.ts`. Test mode by default; live mode requires `--live`. \|
		\| `stripekit pull` \| Generate `stripe.config.ts` from your existing catalog (read-only). \|
		\| `stripekit dev` \| Forward Stripe webhooks to your local app and capture the signing secret (wraps `stripe listen`). \|
		\| `stripekit check` \| Doctor: verify keys, config, config-vs-account drift, and webhook/portal wiring. \|
		\| `stripekit mcp` \| Run as an MCP server (stdio) so AI agents can call plan/push/pull/check directly. \|

		@@ -73,4 +80,8 @@ Common flags: `--json` (machine-readable output for agents/CI), `--yes` (skip confirmation — required to apply to live mode non-interactively), `--url <url>` (base URL for webhook registration).

		## For AI agents

		Point your coding agent at [SKILL.md](https://stripe.rafael.ltd/SKILL.md) and it can set stripekit up for you. The docs are also available as [llms.txt](https://stripe.rafael.ltd/llms.txt) / [llms-full.txt](https://stripe.rafael.ltd/llms-full.txt), and every command accepts `--json` and `--yes`. Or run `stripekit mcp` to expose `plan`/`push`/`pull`/`check` to an agent as [MCP](https://modelcontextprotocol.io) tools.

		## License

		MIT

dist/cli.js

Sorry, the diff of this file is too big to display

dist/cli.js.map

Sorry, the diff of this file is too big to display

		# stripekit

		[![npm](https://img.shields.io/npm/v/stripekit.svg)](https://www.npmjs.com/package/stripekit)
		[![CI](https://github.com/rafaelcg/stripekit/actions/workflows/ci.yml/badge.svg)](https://github.com/rafaelcg/stripekit/actions/workflows/ci.yml)
		[![license](https://img.shields.io/npm/l/stripekit.svg)](https://github.com/rafaelcg/stripekit/blob/main/LICENSE)
		[![docs](https://img.shields.io/badge/docs-stripe.rafael.ltd-635bff)](https://stripe.rafael.ltd/)

		The create-next-app of Stripe. Declare your product catalog in a config file, and `stripekit` reconciles your _own_ Stripe account to match it — creating and updating products, prices, the webhook endpoint, and the customer portal. No hosted service, no revenue share, no runtime dependency. Plain Stripe underneath, code you own on top.

		> Status: early. Ships `init`, `plan`, `push`, `pull`, and `dev` (local webhook forwarding). A `check` doctor is on the roadmap.
		> Status: early. Ships `init`, `plan`, `push`, `pull`, `dev` (local webhook forwarding), and `check` (a config/account doctor).

		@@ -44,9 +49,11 @@ ## Why

		\| Command \| What it does \|
		\| ---------------- \| ------------------------------------------------------------------------------------------------------------- \|
		\| `stripekit init` \| Scaffold `stripe.config.ts` and correct-by-construction billing code into a Next.js (App Router) app. \|
		\| `stripekit plan` \| Preview the changes `push` would make. Never mutates anything. \|
		\| `stripekit push` \| Reconcile your Stripe account to match `stripe.config.ts`. Test mode by default; live mode requires `--live`. \|
		\| `stripekit pull` \| Generate `stripe.config.ts` from your existing catalog (read-only). \|
		\| `stripekit dev` \| Forward Stripe webhooks to your local app and capture the signing secret (wraps `stripe listen`). \|
		\| Command \| What it does \|
		\| ----------------- \| ------------------------------------------------------------------------------------------------------------- \|
		\| `stripekit init` \| Scaffold `stripe.config.ts` and correct-by-construction billing code into a Next.js (App Router) app. \|
		\| `stripekit plan` \| Preview the changes `push` would make. Never mutates anything. \|
		\| `stripekit push` \| Reconcile your Stripe account to match `stripe.config.ts`. Test mode by default; live mode requires `--live`. \|
		\| `stripekit pull` \| Generate `stripe.config.ts` from your existing catalog (read-only). \|
		\| `stripekit dev` \| Forward Stripe webhooks to your local app and capture the signing secret (wraps `stripe listen`). \|
		\| `stripekit check` \| Doctor: verify keys, config, config-vs-account drift, and webhook/portal wiring. \|
		\| `stripekit mcp` \| Run as an MCP server (stdio) so AI agents can call plan/push/pull/check directly. \|

		@@ -73,4 +80,8 @@ Common flags: `--json` (machine-readable output for agents/CI), `--yes` (skip confirmation — required to apply to live mode non-interactively), `--url <url>` (base URL for webhook registration).

		## For AI agents

		Point your coding agent at [SKILL.md](https://stripe.rafael.ltd/SKILL.md) and it can set stripekit up for you. The docs are also available as [llms.txt](https://stripe.rafael.ltd/llms.txt) / [llms-full.txt](https://stripe.rafael.ltd/llms-full.txt), and every command accepts `--json` and `--yes`. Or run `stripekit mcp` to expose `plan`/`push`/`pull`/`check` to an agent as [MCP](https://modelcontextprotocol.io) tools.

		## License

		MIT

stripekit - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics

Dependency changes