NEARBuilders / NEARBuilders/everything-dev
orpc-v2: migrate _template scaffold to the new plugin API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 6
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Ticket ID: B4a
Parent
#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)
What to build
Stage B, step 4a: migrate the _template scaffold to the new createPlugin API — Layer-based initialize, no tools/buildService, no context-bridge module. This scaffold is the reference for every future child-repo plugin (bos init), so it must read as the canonical example of the new pattern, including the scaffold's self-documentation.
Acceptance criteria
- Template's integration tests green on the new API
- Scaffold builds via its rspack config; no old-API remnants (tools, context bridge)
- A
bos init-generated scratch child using the scaffold compiles against the branch's every-plugin
Blocked by
- #259 — createPlugin restructure
- #260 — migrate all six contracts to the v2 route builder
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 with the _template scaffold and its integration tests, then inspect the rspack config and the new createPlugin API after blockers #259 and #260 are available. Done means the tests are green, the scaffold builds without tools or a context-bridge module, and a bos init-generated scratch child compiles against the branch's every-plugin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100