@quickback-dev/cli 0.70.6 → 0.70.8

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/dist/index.js CHANGED
@@ -10,7 +10,7 @@
10
10
  */
11
11
  import pc from "picocolors";
12
12
  // Version injected at build time by scripts/inject-version.ts
13
- const CLI_VERSION = "0.70.6";
13
+ const CLI_VERSION = "0.70.8";
14
14
  function getPackageVersion() {
15
15
  return CLI_VERSION;
16
16
  }
@@ -31,8 +31,9 @@ served as `application/problem+json` (see
31
31
  Quickback's contextual fields (`code`, `layer`, `details`, `hint`, `request`)
32
32
  survive as 9457 **extension members**, so clients that switch on `code` keep
33
33
  working. Every structured error also carries a `request` block with the HTTP
34
- method, URL, request ID, and a redacted+truncated copy of the request body —
35
- enough to triage or hand the response to an LLM agent without grepping logs:
34
+ method, URL and request ID — and, when the deploy sets `EXPOSE_ERROR_STACK=1`,
35
+ a redacted, truncated copy of the request body — enough to triage or hand the
36
+ response to an LLM agent without grepping logs:
36
37
 
37
38
  ```json
38
39
  {
@@ -69,7 +70,7 @@ enough to triage or hand the response to an LLM agent without grepping logs:
69
70
  | `details` | object | Extension — layer-specific context (optional) |
70
71
  | `pointer` | string | Extension — first key of `details.fields` for guard and validation failures, e.g. `/stage` (optional) |
71
72
  | `hint` | string | Extension — actionable guidance for resolution (optional) |
72
- | `request` | object | Extension — method, URL, redacted body, and request ID. Auto-attached by the runtime so the error body is self-contained — bodies are capped at 4 KB and well-known sensitive keys (`password`, `token`, `secret`, `apiKey`, `otp`, `code`, `authorization`, …) plus every credential field the compiler itself introduces (`sessionToken`, `eventSessionToken`, `scopeJwt`, `scopeToken`, `wsTicket`, `inviteToken`, `jwt`, `signature`, …) are replaced with `"[REDACTED]"` |
73
+ | `request` | object | Extension — method, URL and request ID, auto-attached by the runtime so an error correlates with the server log. The request body is included only when `EXPOSE_ERROR_STACK=1` is set on the deploy (dev/staging): capped at 4 KB, with well-known sensitive keys (`password`, `token`, `secret`, `apiKey`, `otp`, `code`, `authorization`, …) and every credential field the compiler introduces (`sessionToken`, `eventSessionToken`, `scopeJwt`, `scopeToken`, `wsTicket`, `inviteToken`, `jwt`, `signature`, …) replaced with `"[REDACTED]"`. Off by default because error bodies land in client logs, error UIs and support screenshots, and redaction cannot know every sensitive field a write carries |
73
74
 
74
75
  The per-layer examples below are abbreviated to `detail` plus each layer's
75
76
  extension members — every real response also carries `type`, `title`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quickback-dev/cli",
3
- "version": "0.70.6",
3
+ "version": "0.70.8",
4
4
  "description": "CLI for Quickback — define your backend in TypeScript, compile to a fully wired Cloudflare Worker (or Bun / Node) with auth, database, migrations, security, CMS, and Account UI.",
5
5
  "author": "Kardoe Incorporated <paul@kardoe.com>",
6
6
  "license": "MIT",
@@ -31,8 +31,9 @@ served as `application/problem+json` (see
31
31
  Quickback's contextual fields (`code`, `layer`, `details`, `hint`, `request`)
32
32
  survive as 9457 **extension members**, so clients that switch on `code` keep
33
33
  working. Every structured error also carries a `request` block with the HTTP
34
- method, URL, request ID, and a redacted+truncated copy of the request body —
35
- enough to triage or hand the response to an LLM agent without grepping logs:
34
+ method, URL and request ID — and, when the deploy sets `EXPOSE_ERROR_STACK=1`,
35
+ a redacted, truncated copy of the request body — enough to triage or hand the
36
+ response to an LLM agent without grepping logs:
36
37
 
37
38
  ```json
38
39
  {
@@ -69,7 +70,7 @@ enough to triage or hand the response to an LLM agent without grepping logs:
69
70
  | `details` | object | Extension — layer-specific context (optional) |
70
71
  | `pointer` | string | Extension — first key of `details.fields` for guard and validation failures, e.g. `/stage` (optional) |
71
72
  | `hint` | string | Extension — actionable guidance for resolution (optional) |
72
- | `request` | object | Extension — method, URL, redacted body, and request ID. Auto-attached by the runtime so the error body is self-contained — bodies are capped at 4 KB and well-known sensitive keys (`password`, `token`, `secret`, `apiKey`, `otp`, `code`, `authorization`, …) plus every credential field the compiler itself introduces (`sessionToken`, `eventSessionToken`, `scopeJwt`, `scopeToken`, `wsTicket`, `inviteToken`, `jwt`, `signature`, …) are replaced with `"[REDACTED]"` |
73
+ | `request` | object | Extension — method, URL and request ID, auto-attached by the runtime so an error correlates with the server log. The request body is included only when `EXPOSE_ERROR_STACK=1` is set on the deploy (dev/staging): capped at 4 KB, with well-known sensitive keys (`password`, `token`, `secret`, `apiKey`, `otp`, `code`, `authorization`, …) and every credential field the compiler introduces (`sessionToken`, `eventSessionToken`, `scopeJwt`, `scopeToken`, `wsTicket`, `inviteToken`, `jwt`, `signature`, …) replaced with `"[REDACTED]"`. Off by default because error bodies land in client logs, error UIs and support screenshots, and redaction cannot know every sensitive field a write carries |
73
74
 
74
75
  The per-layer examples below are abbreviated to `detail` plus each layer's
75
76
  extension members — every real response also carries `type`, `title`,