Repository navigation
chore: upgrade template to stable Effect 4 - #19
Merged
Merged
Conversation
lloydrichards
force-pushed
the
chore/v4-migrate
branch
from
May 20, 2026 19:16
e79dd5b to
0370d4e
Compare
lloydrichards
changed the title
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
1 participant
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.
Goals/Scope
Upgrade the template to stable Effect 4.0.0 and current workspace dependencies so new repositories can start from
mainafter merge.Review the Effect API changes, stream lifecycle fixes, and setup instructions. Success means a fresh template passes lint, formatting, types, tests, builds, and browser checks.
Description
Migrate the client, servers, and shared packages to Effect 4 APIs:
Use TypeScript 7 with the patched
@effect/tsgocompiler. Refresh README, package docs, agent guidance, and.env.example.Fix two stream bugs: the tick stream could lose its final event, and presence could miss updates published before its subscription started. End the tick queue with
Queue.endand acquire the presence subscription before broadcasting.Repair Docker ports, browser URLs, API-key configuration, and trace export to Jaeger. Remove personal folder requirements from the development container, refresh the Nix lock, and add CI checks for every workspace.