Repository navigation
docs(packages): what kody dev does while it runs, kody.dev settings, agent mode - #3829
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
…agent mode Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
… SSR Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
6a898d9 to
beb33bf
Compare
|
Unblocked and ready to ship Verified before marking ready:
Following ship-pr from here (CI + Bugbot → merge). |
|
🔎 Preview deployed: https://kody-pr-3829.kody-a99.workers.dev Worker: Seed login (public preview fixture)
Prefer MCP/API/
Do not post session cookies or tokens in PR comments. Mocks:
|
Intent
Document the improved
kody dev(from the@kodycodes/clichanges) in the package guides that agents read.Door:
two-wayCleanup:
noneWhy
kody devnow has zero-downtime rebuilds, real error pages and logs, live reload, an agent mode (--json,/__kody/dev/status, attach), stable ports, localkody.app.client/kody.app.assetsserving, and akody.dev.prebuildhook. The guides only said "serves on localhost with hot reload", so agents can't discover any of this.Local bundling also now treats bare Node builtins (
stream,fs/promises, …) the way publish does. Server-side rendering with a package's Node build still fails at request time in an ES module Worker, so the guide says to use the Workers/edge entry. The@kentcdodds/package-app-kitTanStack starter hits exactly this case.Summary
docs/guides/package-apps.md, section "Local testing withkody dev":kody devdoes while it runs (rebuilds, error pages, logs, live reload,/_assetsparity, ports);package.json#kody.devblock (prebuild,ignore) with an example;kody dev fetchattach,--json,--ready-file, the status endpoint).docs/guides/package-apps.md, "Fetch handlers": the entry runs withnodejs_compat, so builtins stay external in publish and dev. A CommonJSrequire()of a builtin throws "Dynamic require of … is not supported". Import the Workers/edge entry instead, for examplereact-dom/server.edgeforrenderToReadableStream.docs/guides/package-lifecycle.md: the Apps row of the local CLI testing table mentions--jsonfor agents.Referenced issues and PRs
Unblocked: the
kody devCLI changes in kody-bot/cli PRs #58–#69 are merged and released in@kodycodes/cli@1.26.2(tagv1.26.2= merge of #69). Docs event list and behavior match that release (including later polish in #64–#69: package-graph sizing is internal; JSON event types unchanged;dev fetch --jsonstill emitsbuild_error).Testing
oxfmtran in the pre-commit hook;node tools/check-docs-no-hosted-execute.tspasses.dev-eventstypes in@kodycodes/cli@1.26.2. For the edge-entry note, a minimal app onreact-dom/serverreturned 500 with "Dynamic require of "util"", and the same app onreact-dom/server.edgereturned 200.mainbefore marking ready.Note
Low Risk
Documentation-only updates to package guides; no runtime, auth, or application code changes.
Reviewed by Cursor Bugbot for commit beb33bf. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
kody devguide with details on rebuild requests, development errors, request-tagged console output, HTML live reload, local asset URLs, port selection, and development settings.kody dev fetch, its JSON readiness and event output, and the status endpoint.require()calls for built-ins fail at request time and that dependencies targeting Node builds should use Workers or edge entries.--jsonoutput.