Repository navigation
docs: add an oRPC definition and quick example to READMEs - #2312
Conversation
The root README and the package READMEs shown on npm went straight from badges to the package table, so neither readers nor search engines and AI assistants got a plain statement of what oRPC is. Add a short definition and a minimal router/client example to every copy, and give the documentation link descriptive text instead of "here". Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EHxSoP6NZjYvqLsw6itB38
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — This PR only adds descriptive README text, fenced usage examples, and clearer documentation links across the repository and package READMEs. It does not modify executable code or production behavior. You can add or adjust custom eligibility rules. Learn more. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
orpc | 9f8ceae | Commit Preview URL Branch Preview URL |
Oct 23 2026, 02:51 AM |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — docs-only change adding an identical definition + quick example block to the root and 29 package READMEs.
- Definition added — a two-sentence plain-English definition of oRPC placed after the badges, consistent with the
index.astrometa description andHero.astrowording. - Quick example added — a server router (
os.input(...).handler(...)) and client (RPCLink({ origin, url })+createORPCClient+RouterClient<typeof router>) snippet. - Documentation line rewritten — replaced the
[here]link with an explicitorpc.devlink and a Getting Started guide link.
All 30 added blocks are byte-identical, the example matches apps/content/docs/getting-started.mdx (the origin + url options on RPCLink are the current v2 API), planet.find correctly types as { id: number, name: string }, and both new links resolve (/docs/rpc/handler and /docs/getting-started both exist). The fan-out across every README follows the existing duplicated-badge convention and is not touched by the Sponsors sync.
deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏
More templates
@orpc/ai-sdk
@orpc/arktype
@orpc/bun
@orpc/client
@orpc/cloudflare
@orpc/contract
@orpc/experimental-effect
@orpc/evlog
@orpc/hibernation
@orpc/json-schema
@orpc/experimental-lock
@orpc/mcp
@orpc/msw
@orpc/nest
@orpc/next
@orpc/node
@orpc/openapi
@orpc/opentelemetry
@orpc/pinia-colada
@orpc/pino
@orpc/publisher
@orpc/ratelimit
@orpc/server
@orpc/shared
@orpc/swr
@orpc/tanstack-query
@orpc/trpc
@orpc/valibot
@orpc/zod
commit: |
Merging this PR will not alter performance1 warning
Comparing Footnotes
|

Requested by dinwwwh · project thread
Summary
The root README and the 29 package READMEs (the pages people see on npm) go straight from the badges to the package table, so nothing on them says what oRPC is. Search engines and AI assistants read these pages heavily, and they had no plain definition to quote.
This adds the same short block to every README, right after the badges:
planet.findexample used on the home page and in Getting Started, written with the v2 API (origin+urlonRPCLink).The package READMEs are still identical to the root README below the badges, so they stay easy to keep in sync.
Verification
tscagainst the workspace packages. They compile, andplanetresolves to{ id: number, name: string }(assigning it tostringfails as expected, so it is notany).pnpm lintpasses (ESLint also lints the code blocks in Markdown).Generated by Claude Code