NEARBuilders / NEARBuilders/everything-dev
orpc-v2: all five plugins on Effect 4
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 6
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Ticket ID: A4
Parent
#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)
What to build
Stage A, step 3: migrate all five plugins (template, apps, auth, proposals, votes) to Effect 4 — service layers, db migrators, tests — still building against the current every-plugin API. Each plugin's bundle must build and load via Module Federation with the shared effect singleton.
Acceptance criteria
- All five plugins' test suites green on
effect 4.0.0-rc.112 - All five rspack builds succeed;
bos devloads each plugin -
bos mf checkclean (single effect version across remotes)
Blocked by
- #254 — every-plugin on Effect 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the #254 dependency, then inspect the template, apps, auth, proposals, and votes plugins, including their service layers, DB migrators, and tests. Verify each test suite and rspack build, run bos dev to load every plugin, and finish with a clean bos mf check showing one shared Effect version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100