docs: add server-side TypeScript connection lifecycle#5005
Closed
benpsnyder wants to merge 1 commit into
Closed
Conversation
Contributor
|
Hi @benpsnyder, thanks for your contribution to the docs. We don't accept draft PRs in our repo to keep our PRs relatively neat and manageable, so I'm going to close this for now, at least until you have a complete PR for us to review. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refs #5004.
Adds server-side TypeScript lifecycle guidance for generated
DbConnectionusage from Node/server runtimes. This covers long-running connection managers, reconnect/resubscribe behavior, reducer calls from server handlers, token refresh by rebuilding connections, request-scoped/serverless snapshots, and an optional Effect v4 runtime pattern for testable services and CLI workflows.Also adds TypeScript reference notes for Node.js runtime requirements, including Node 22 global WebSocket support and
undicion Node 18-21.Verification
git diff --checkpnpm --dir docs buildwith Node v22.22.2pnpm --dir docs typecheckwith Node v22.22.2Build note: an initial workspace install failed under Node v26 and then under full workspace install due unrelated native/optional dependency install issues. A filtered docs install with scripts ignored succeeded, and the docs build/typecheck passed under Node v22.22.2.