+1
-1
@@ -74,3 +74,3 @@ /** | ||
| /** Where the generated `sync.ts` persists canonical customer state. */ | ||
| type SyncAdapter = 'drizzle' | 'kv' | 'prisma'; | ||
| type SyncAdapter = 'drizzle' | 'kv'; | ||
| interface StripekitConfig { | ||
@@ -77,0 +77,0 @@ /** The products in your catalog, keyed by a stable slug (`pro`, `team`). */ |
+1
-1
| { | ||
| "name": "stripekit", | ||
| "version": "0.1.0", | ||
| "version": "0.1.1", | ||
| "description": "The create-next-app of Stripe. Declarative catalog reconciliation into your own Stripe account, plus correct-by-construction billing code you own.", | ||
@@ -5,0 +5,0 @@ "license": "MIT", |
+1
-1
@@ -9,3 +9,3 @@ # stripekit | ||
| The painful parts of Stripe aren't the API calls — they're the dashboard ceremony, the test/live drift, and getting webhooks + state sync correct. Existing tools either replace your Stripe account (merchants of record) or put your billing state on their servers (hosted control planes). stripekit does neither: it's a dev tool that leaves you with a declarative catalog and, soon, correct-by-construction code in your repo. | ||
| The painful parts of Stripe aren't the API calls — they're the dashboard ceremony, the test/live drift, and getting webhooks + state sync correct. Existing tools either replace your Stripe account (merchants of record) or put your billing state on their servers (hosted control planes). stripekit does neither: it's a dev tool that leaves you with a declarative catalog and correct-by-construction code in your repo. | ||
@@ -12,0 +12,0 @@ ## Install |
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is too big to display
Deprecated
MaintenanceThe maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
253044
0.36%2572
0.19%0
-100%