Skip to content

Commit 75cc0f0

Browse files
committed
docs(quickstart): re-transcribe both boot samples against CLI 17.4.0
Both paths re-booted on @objectstack/cli 17.4.0 as independent pty captures and diffed against the published blocks; every difference classified against a 17.3.0 control resolved as of before better-auth 1.7.3 shipped (all 55 @objectstack packages read back at 17.3.0). - Pins 17.3.0 -> 17.4.0 on both blocks. - Path B Build complete timing re-transcribed from this capture (97ms). - Both declarations drop the SQL driver's schema-sync notes (gone at 17.4.0) and name the two new SQL-driver error lines instead. - Path B's declaration drops boot diagnostics (gone at 17.4.0) and stops pinning the MCP trailer "above the banner": a separate process prints it, and its position was measured varying between boots at 17.3.0 and at 17.4.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FeA1nwBz1ohH65dvffUGKr
1 parent c2d1181 commit 75cc0f0

1 file changed

Lines changed: 13 additions & 8 deletions

File tree

‎content/docs/quickstart.mdx‎

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -60,12 +60,14 @@ You'll see:
6060

6161
That's it. You're running ObjectOS.
6262

63-
That block is transcribed from `@objectstack/cli` 17.3.0 booting an empty
63+
That block is transcribed from `@objectstack/cli` 17.4.0 booting an empty
6464
kernel. Home paths show as `~/…` — the CLI prints yours expanded. Your own boot
6565
also prints a `No objectstack.config.ts or artifact found` line before the
6666
server starts, plus startup advisories (local storage driver, dev crypto key,
67-
schema-sync notes from the SQL driver, boot diagnostics) and the full list of
68-
loaded plugin names, both of which depend on your environment.
67+
boot diagnostics) and the full list of loaded plugin names, both of which
68+
depend on your environment. It also logs two SQL-driver errors that do not stop
69+
the server: a `DATABASE_ERROR` for a missing `_objectstack_sequences` table, and
70+
an `Insert operation failed` on `sys_oauth_resource` with a stack trace.
6971

7072
### What's running
7173

@@ -160,7 +162,7 @@ You'll see:
160162
161163
◆ Compile
162164
────────────────────────────────────────
163-
✓ Build complete (143ms)
165+
✓ Build complete (97ms)
164166
165167
Data: 1 Objects 3 Fields
166168
UI: 0 Apps
@@ -196,13 +198,16 @@ You'll see:
196198
```
197199

198200
That block is transcribed from `pnpm dev` on a scaffold created by
199-
`@objectstack/cli` 17.3.0. Project paths show as `my-app/…` — the CLI prints
201+
`@objectstack/cli` 17.4.0. Project paths show as `my-app/…` — the CLI prints
200202
yours expanded, and the `Build complete` timing is whatever the transcribing
201203
machine measured, so yours will differ. Your own run also prints pnpm's script
202204
header above the block, per-step compile progress, startup advisories
203-
(configuration load, dev secret-field crypto, schema-sync notes from the SQL
204-
driver), the full list of loaded plugin names, boot diagnostics, and an MCP
205-
connection trailer above the banner.
205+
(configuration load, dev secret-field crypto), the full list of loaded plugin
206+
names, and an MCP connection trailer. A separate process prints that trailer,
207+
so it usually follows `Press Ctrl+C to stop` but can land inside the banner. The
208+
run also logs SQL-driver errors that do not stop the server: a `DATABASE_ERROR`
209+
for a missing `_objectstack_sequences` table (printed twice), and an
210+
`Insert operation failed` on `sys_oauth_resource` with a stack trace.
206211

207212
Note the dev server asks for port **3000**, the same port `os start` uses. If
208213
that port is taken it binds the next free one and says so:

0 commit comments

Comments
 (0)