orpc-v2: Effect 4 + oRPC v2 feasibility spike (hard gate)

Open
#253 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend-api-design, build-system, testing

Research direction

Use a throwaway branch and begin by bumping the catalog to effect 4.0.0-rc.112, then run the repository install, build, and typecheck. Check @effect/vitest, @effect/language-service, @orpc/experimental-effect, and Module Federation sharing, while inventorying affected idioms across every-plugin runtime services, host, api, and plugins. Done means posting the breaking-change findings and a go/no-go comment here.

Written by the indexing model from the issue text.

Description

ready-for-agent

Ticket ID: A1

Parent

#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)

What to build

Hard-gate spike for Stage A: prove the platform toolchain works on Effect 4 before touching any package for real. On a throwaway branch:

  • Bump the catalog to effect 4.0.0-rc.112 repo-wide; install, build, typecheck.
  • Verify @effect/vitest works with the repo's vitest setup (or document the fallback).
  • Verify @effect/language-service still applies (or drop it consciously).
  • Inventory the Effect 3.21.2 idioms that break in Effect 4 across every-plugin runtime services, host, api, and plugins (Layer/service/context APIs in use).
  • Confirm @orpc/experimental-effect's peer (effect >= 4.0.0-beta.90) resolves cleanly.
  • Check Module Federation shared singletons: exactly one effect copy across remotes.

Publish the findings as a comment on this issue with a go/no-go. If no-go, stop the epic and re-plan — A2/A3 must not start without the go.

Acceptance criteria

  • Spike branch builds + typechecks on effect 4.0.0-rc.112 repo-wide
  • Vitest runs green under @effect/vitest (fallback documented if not)
  • Breaking-change inventory + go/no-go recorded as a comment here
  • Go decision made before A2/A3 begin

Blocked by

  • #250 — merge citynode.app into everything-dev main
Dominant language
TypeScript
Stars
5
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NEARBuilders/everything-dev

All issues in NEARBuilders/everything-dev

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.