Skip to content

docs: scaffolding guide for connectum init / generate service#64

Open
intech wants to merge 3 commits into
mainfrom
docs/cli-scaffolding
Open

docs: scaffolding guide for connectum init / generate service#64
intech wants to merge 3 commits into
mainfrom
docs/cli-scaffolding

Conversation

@intech

@intech intech commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the new scaffolding commands shipped in @connectum/cli (companion to the framework PR that adds connectum init and connectum generate service).

Changes

  • New guide page en/guide/scaffolding.md — "Scaffolding a New Service":
    • connectum init flow (interactive wizard and non-interactive flags) with a full options table
    • the deterministic interceptor order emitted when several interceptor-adding modules are selected (OpenTelemetry → error handler → auth → validation → resilience → custom)
    • connectum generate service, including why it prints the registration line instead of editing your src/server.ts
    • the plain "add a service by hand" recipe (proto → buf generatedefineService → register)
  • Sidebar — the page is listed under Introduction, right after Quickstart
  • en/contributing/cli-commands.md — a tip clarifying that this page covers monorepo development scripts, and pointing to the scaffolding guide for the published CLI tool
  • en/guide/runtime-compatibility.md — a tip noting the Bun limitations are narrow (they affect the HTTP/2 client transport, not the server) and that a scaffolded Bun project already gets Bun-appropriate defaults; restates the Node floor (raw .ts >= 25.2 vs tsx/compiled >= 22.13)

🤖 Generated with Claude Code

https://claude.ai/code/session_01SdapMMJeamn5TDrY8yzHRQ

- new guide page en/guide/scaffolding.md (init flow, options table, interceptor order,
  generate service, the add-a-service recipe) + sidebar entry after Quickstart
- cli-commands.md: point to the scaffolding guide for the published @connectum/cli tool
- runtime-compatibility.md: note the Bun caveats are narrow (client transport) and that
  scaffolding emits Bun-appropriate defaults; restate the Node floor (raw .ts >=25.2 vs
  tsx/compiled >=22.13)

Companion docs for the connectum cli-scaffolding change (Phase 4, tasks 4.1-4.3).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SdapMMJeamn5TDrY8yzHRQ
intech and others added 2 commits July 21, 2026 08:45
Rebased onto main after the runtime-switcher PR landed, and corrected content that it
made stale:

- `runtime-compatibility.md`: my earlier tip claimed the Bun limitations were "narrow —
  the HTTP/2 client transport". That is no longer true: main now documents that
  Bun >= 1.2.6 needs no special client code. The tip now only states what still holds —
  `init --runtime bun` emits Bun-appropriate defaults — and adds the newly documented
  guidance that the CLI is exercised on Node.js, so it should be run with `npx` even in
  a Bun project.
- `scaffolding.md`: same `npx` note in Requirements, plus the generated `start`/`test`
  scripts are now shown through the `::: runtime` switcher (Node | Bun) instead of prose,
  and it is stated that the generated e2e test is runtime-agnostic (in-process
  `createLocalClient`, no socket).

`vitepress build` passes; the built page contains both switcher branches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SdapMMJeamn5TDrY8yzHRQ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type:docs Documentation: guides, README, JSDoc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant