apiblaze 0.3.0 → 0.3.2
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 +14 -0
- package/dist/index.js +600 -320
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -36,6 +36,9 @@ npx apiblaze dev
|
|
|
36
36
|
# Or specify a port
|
|
37
37
|
npx apiblaze dev 3000
|
|
38
38
|
|
|
39
|
+
# Stream full request/response traffic to a file (JSON lines)
|
|
40
|
+
npx apiblaze dev 3000 --capture-file traffic.jsonl
|
|
41
|
+
|
|
39
42
|
```
|
|
40
43
|
|
|
41
44
|
## Help
|
|
@@ -70,6 +73,17 @@ apiblaze help dev
|
|
|
70
73
|
|
|
71
74
|
On Ctrl+C the tunnel is cleanly deregistered.
|
|
72
75
|
|
|
76
|
+
### Zero-setup conveniences
|
|
77
|
+
|
|
78
|
+
- **No project yet?** If none of your projects point at this machine, `apiblaze dev`
|
|
79
|
+
offers to spin up a throwaway dev proxy (random name like `braveotter42`) pointed at
|
|
80
|
+
`http://localhost:<port>` and tunnels it immediately — pick `none` or `api_key` auth.
|
|
81
|
+
- **Server not running yet?** If nothing is listening on the local port, requests aren't
|
|
82
|
+
dropped: each one is printed in full (headers + body, with API keys/JWTs masked and JWTs
|
|
83
|
+
decoded) and answered with a friendly synthetic `200`. The moment your dev server comes
|
|
84
|
+
up, the next request forwards to it automatically. Add `--capture-file <path>` to also
|
|
85
|
+
stream every request/response to a JSON-lines file.
|
|
86
|
+
|
|
73
87
|
## License
|
|
74
88
|
|
|
75
89
|
MIT
|