NEARBuilders / NEARBuilders/everything-dev
orpc-v2: deps bump + every-plugin v2 surface (barrels, route extension, publisher rename)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 6
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Ticket ID: B1
Parent
#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)
What to build
Stage B, step 1 — the expand step on the orpc-v2 integration branch. Bump all @orpc/* packages to 2.0.0-beta.35, add @orpc/experimental-effect (peer effect >= 4.0.0-beta.90, satisfied by Stage A) and @orpc/publisher, and rewrite every-plugin's public surface for v2:
- Barrel rewrite: publisher imports move to
@orpc/publisher(MemoryPublisherfrom@orpc/publisher/memory;resumeRetentionSeconds→resume: { enabled, seconds };publish()is async — background loops must await). - Preload the
@orpc/openapiroute extension so downstream contract builders get full OpenAPIMeta on.route. - Simplify the errors module's status handling for v2 (its status-stripping call sites move to errorStatusMap semantics, landed in B2/B5).
- Keep Module Federation shared-dependency declarations in sync across every place that enumerates them (catalog, every-plugin build config, host, ui).
Monorepo-red is expected from here until B6 — every-plugin's own suite is the green gate for this ticket.
Acceptance criteria
- All
@orpc/*at2.0.0-beta.35;@orpc/publisherreplaces experimental-publisher;@orpc/experimental-effectadded - every-plugin barrel exports the v2 surface with the route extension preloaded
- every-plugin's own unit + integration suites green
-
bos mf checkclean on the branch
Blocked by
- #257 — Stage A integrate and verify
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
Wait for #257, then inspect every-plugin's barrel and errors module, the Module Federation declarations in the catalog, build config, host, and ui, and the existing unit and integration suites. Trace the current publisher and route-extension imports before making the v2 surface consistent. Done means every-plugin's suites are green and bos mf check is clean with all listed package versions and exports updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100