saasfunnels 0.3.2 → 0.3.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/dist/library.js +211555 -11
- package/dist/saasfunnels.js +935 -398
- package/dist/types/feature-setup.d.ts +2 -0
- package/dist/types/identity.d.ts +1 -1
- package/dist/types/mcp.d.ts +1 -1
- package/dist/types/setup-pricing.d.ts +21 -0
- package/dist/types/source-analysis.d.ts +15 -0
- package/dist/types/source-scope.d.ts +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -108,4 +108,14 @@ Static pricing supports literal spreads, capability/quota maps, unlimited limits
|
|
|
108
108
|
|
|
109
109
|
If extraction is unsupported, `.saasfunnels/setup-review.json` lists the files and reasons. Correct those declarations or review a `.saasfunnels/setup-pricing.json` file with `{ "plans": [{ "key": "pro", "name": "Pro", "features": { "export": true }, "prices": [{ "key": "price_ACTUAL_ID" }] }] }`, then resume. Use real identifiers from the connected merchant. Raw source files are never uploaded by guided setup or the pricing handoff.
|
|
110
110
|
|
|
111
|
+
Discovery follows Git ignore rules (including custom build folders) while keeping tracked application sources and new, non-ignored source files. Standalone folders without Git use the standard source filters.
|
|
112
|
+
|
|
111
113
|
The command does not implement arbitrary payment code, approve feature access, or verify transactions. Complete **Review and verify** in Setup after deploying the runtime and payment integration. Requires the server's guided setup API release.
|
|
114
|
+
|
|
115
|
+
### Discovery accuracy and review
|
|
116
|
+
|
|
117
|
+
Guided setup proposes supported JavaScript/TypeScript gates and static JS/TS/JSON/YAML catalogs. Tests, fixture/demo scopes, comments, and generic role permissions are excluded. Named capabilities and numeric/unlimited limits remain separate; units, reset periods, and aggregation require review in Setup's existing Plans & pricing editor.
|
|
118
|
+
|
|
119
|
+
A frontend scan is not evidence of complete backend coverage. Setup flags unsupported application languages, unresolved dynamic access, and optional add-on/capacity/trial declarations. Review these against the actual application's entitlement owner before confirming. Imported or dynamic pricing that cannot be statically resolved needs reviewed literal `.saasfunnels/setup-pricing.json` evidence or manual configuration; source is never executed. Arbitrary helper names and external services cannot be exhaustively discovered automatically.
|
|
120
|
+
|
|
121
|
+
Feature configuration must be saved and published in Plans & pricing before Setup can confirm it. Naming an unnamed restriction records a review decision; it does not implement access. A new scanner version may require running without `--resume`; guided rescans preserve human decisions and leave local generated catalogs untouched.
|