@quickback-dev/cli 0.66.6 → 0.66.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/commands/build.d.ts +0 -1
- package/dist/commands/build.d.ts.map +1 -1
- package/dist/commands/build.js +0 -1
- package/dist/commands/build.js.map +1 -1
- package/dist/index.js +1 -1
- package/dist/lib/api-client.d.ts +1 -1
- package/dist/lib/api-client.d.ts.map +1 -1
- package/dist/lib/api-client.js +13 -8
- package/dist/lib/api-client.js.map +1 -1
- package/dist/lib/api-client.test.js +47 -0
- package/dist/lib/api-client.test.js.map +1 -1
- package/dist/lib/file-writer.d.ts +1 -1
- package/dist/lib/file-writer.d.ts.map +1 -1
- package/dist/lib/file-writer.js +2 -3
- package/dist/lib/file-writer.js.map +1 -1
- package/dist/lib/migrations/drizzle.d.ts.map +1 -1
- package/dist/lib/migrations/drizzle.js +6 -1
- package/dist/lib/migrations/drizzle.js.map +1 -1
- package/dist/lib/migrations/drizzle.test.js +7 -0
- package/dist/lib/migrations/drizzle.test.js.map +1 -1
- package/dist/lib/migrations/executor.d.ts.map +1 -1
- package/dist/lib/migrations/executor.js +4 -0
- package/dist/lib/migrations/executor.js.map +1 -1
- package/dist/lib/migrations/postprocessors/better-auth-upgrade.d.ts +7 -0
- package/dist/lib/migrations/postprocessors/better-auth-upgrade.d.ts.map +1 -0
- package/dist/lib/migrations/postprocessors/better-auth-upgrade.js +149 -0
- package/dist/lib/migrations/postprocessors/better-auth-upgrade.js.map +1 -0
- package/dist/skill/docs/define/actions/index.md +6 -0
- package/dist/skill/docs/define/actions/scoped-db.md +88 -41
- package/dist/skill/docs/define/transitions.md +11 -0
- package/dist/skill/docs/define/triggers.md +4 -0
- package/dist/skill/docs/platform/auth/index.md +37 -0
- package/dist/skill/docs/platform/database/d1.md +2 -2
- package/dist/skill/docs/platform/database/neon.md +246 -55
- package/dist/skill/docs/platform/queues/handlers.md +12 -0
- package/dist/skill/docs/platform/schedules/index.md +3 -1
- package/dist/skill/docs/tooling/cloud-compiler/endpoints.md +10 -0
- package/dist/skill/docs/tooling/cloud-compiler/troubleshooting.md +16 -0
- package/package.json +1 -1
- package/src/skill/docs/define/actions/index.md +6 -0
- package/src/skill/docs/define/actions/scoped-db.md +88 -41
- package/src/skill/docs/define/transitions.md +11 -0
- package/src/skill/docs/define/triggers.md +4 -0
- package/src/skill/docs/platform/auth/index.md +37 -0
- package/src/skill/docs/platform/database/d1.md +2 -2
- package/src/skill/docs/platform/database/neon.md +246 -55
- package/src/skill/docs/platform/queues/handlers.md +12 -0
- package/src/skill/docs/platform/schedules/index.md +3 -1
- package/src/skill/docs/tooling/cloud-compiler/endpoints.md +10 -0
- package/src/skill/docs/tooling/cloud-compiler/troubleshooting.md +16 -0
|
@@ -150,6 +150,13 @@ The compiler:
|
|
|
150
150
|
2. Extracts top-level `const` declarations (including multi-line template literals)
|
|
151
151
|
3. Inlines them in the generated queue consumer
|
|
152
152
|
|
|
153
|
+
Write static relative imports from your authored file's location. For example,
|
|
154
|
+
from `quickback/services/queues/ingest.ts`, import a feature helper with
|
|
155
|
+
`../../features/materials/lib/process`. The compiler relocates that import to
|
|
156
|
+
`./features/materials/lib/process` in `src/queue-consumer.ts`. Multiline imports
|
|
157
|
+
and mixed value/type imports retain their declarations. Package imports keep
|
|
158
|
+
their package specifiers.
|
|
159
|
+
|
|
153
160
|
## Dynamic Schema Imports
|
|
154
161
|
|
|
155
162
|
Since your schema files are generated by Quickback, use dynamic imports to reference them:
|
|
@@ -170,6 +177,11 @@ execute: async ({ message, db }) => {
|
|
|
170
177
|
|
|
171
178
|
## Sending to Other Queues
|
|
172
179
|
|
|
180
|
+
Queue producers configured through the database's `additionalQueues` or
|
|
181
|
+
`bindings.queueProducers` are included in generated `CloudflareBindings` as
|
|
182
|
+
`Queue` bindings, including `send` and `sendBatch`. They are available from
|
|
183
|
+
schedules and actions as well as queue handlers.
|
|
184
|
+
|
|
173
185
|
Chain queue handlers by sending messages to other queues:
|
|
174
186
|
|
|
175
187
|
```typescript
|
|
@@ -124,7 +124,9 @@ The generated `scheduled()` dispatcher runs every schedule whose cron matches `e
|
|
|
124
124
|
|
|
125
125
|
## Cron syntax
|
|
126
126
|
|
|
127
|
-
Standard Cloudflare cron (`minute hour day-of-month month day-of-week`)
|
|
127
|
+
Standard Cloudflare cron (`minute hour day-of-month month day-of-week`). Step
|
|
128
|
+
expressions such as `*/5 * * * *` are supported directly; the generated runner
|
|
129
|
+
preserves the exact expression for dispatch:
|
|
128
130
|
|
|
129
131
|
| Pattern | Runs |
|
|
130
132
|
|---------|------|
|
|
@@ -119,3 +119,13 @@ On failure, an `error` event is emitted in either protocol:
|
|
|
119
119
|
event: error
|
|
120
120
|
data: { "error": "Compilation failed", "code": "...", "message": "..." }
|
|
121
121
|
```
|
|
122
|
+
|
|
123
|
+
`message` is a **hit list, not a single error**. Independent validation
|
|
124
|
+
failures across features and tables are collected and reported together —
|
|
125
|
+
when more than one exists, the message opens with
|
|
126
|
+
`Found N independent errors — fix ALL of them before recompiling:` followed by
|
|
127
|
+
a numbered list. Fix every entry before recompiling; fixing only the first and
|
|
128
|
+
recompiling wastes a round trip. (Errors from different compile phases — e.g.
|
|
129
|
+
a feature that fails to parse and a resource-config violation — can still
|
|
130
|
+
arrive in successive compiles, since a feature that doesn't parse can't have
|
|
131
|
+
its resource config validated.)
|
|
@@ -13,6 +13,22 @@ quickback login
|
|
|
13
13
|
|
|
14
14
|
Large projects may take longer to compile. The cloud compiler uses [Cloudflare Containers](https://developers.cloudflare.com/containers/) to run compilation in isolated environments. If you hit timeouts, try [running the compiler locally](/tooling/cloud-compiler/local-compiler).
|
|
15
15
|
|
|
16
|
+
## Compiler stays on loading
|
|
17
|
+
|
|
18
|
+
The cloud gateway checks the compiler container with a five-second deadline.
|
|
19
|
+
A container that is warming or does not answer reports `status: "loading"`;
|
|
20
|
+
`status: "ready"` requires the compiler itself to report readiness. The CLI
|
|
21
|
+
limits each health request to ten seconds and retries within a four-minute
|
|
22
|
+
elapsed-time budget before reporting an error. These limits include response
|
|
23
|
+
body reads, so a stalled connection cannot leave the CLI waiting indefinitely.
|
|
24
|
+
|
|
25
|
+
A successful container lifecycle check alone does not prove compilation works.
|
|
26
|
+
After restarting or replacing an unhealthy instance, check `/health` and compile
|
|
27
|
+
an example project. If HTTP remains unresponsive, inspect Cloudflare container
|
|
28
|
+
logs and networking rather than repeatedly restarting the same instance. You
|
|
29
|
+
can use the [local Docker compiler](/tooling/cloud-compiler/local-compiler) while
|
|
30
|
+
the hosted service is unavailable.
|
|
31
|
+
|
|
16
32
|
## "Command not found: quickback"
|
|
17
33
|
|
|
18
34
|
Make sure the CLI is installed globally:
|