chore: migrate to standard-server/* packages

[dinwwwh]

Standard Server moved to the middleapi/standard-server repository and republished under the @standard-server/* npm scope. This switches every package, test, playground, and docs sample to the new scope at ^0.9.0 and points the docs at the new repository.

Changes

• All @standardserver/* imports and dependencies are now @standard-server/* at ^0.9.0; the old scope no longer appears anywhere in the repo.
• Docs links to the Standard Server README now use the new repository URL. All four referenced anchors exist in the new README.
• minimumReleaseAgeExclude lists the fresh 0.9.0 releases so installs are not blocked by the release-age gate; the Dependabot group matches the new scope.

Compatibility

0.9.0 is a rename-only release: typings and runtime are identical to 0.8.3 apart from the global symbol keys for event metadata (STANDARDSERVER_* → STANDARD_SERVER_*). Nothing in oRPC references those keys directly, but an app that ends up with both scopes installed would not share event metadata between them.

Testing

• pnpm type:check and pnpm lint pass.
• Root vitest, @orpc/bun, and @orpc/cloudflare suites pass.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[pkg-pr-new]

More templates

• @orpc/bun-playground
• @orpc/cloudflare-playground
• @orpc/nest-playground
• @orpc/next-playground

@orpc/ai-sdk

npm i https://pkg.pr.new/@orpc/ai-sdk@1990

@orpc/arktype

npm i https://pkg.pr.new/@orpc/arktype@1990

@orpc/bun

npm i https://pkg.pr.new/@orpc/bun@1990

@orpc/client

npm i https://pkg.pr.new/@orpc/client@1990

@orpc/cloudflare

npm i https://pkg.pr.new/@orpc/cloudflare@1990

@orpc/contract

npm i https://pkg.pr.new/@orpc/contract@1990

@orpc/experimental-effect

npm i https://pkg.pr.new/@orpc/experimental-effect@1990

@orpc/evlog

npm i https://pkg.pr.new/@orpc/evlog@1990

@orpc/hibernation

npm i https://pkg.pr.new/@orpc/hibernation@1990

@orpc/json-schema

npm i https://pkg.pr.new/@orpc/json-schema@1990

@orpc/experimental-msw

npm i https://pkg.pr.new/@orpc/experimental-msw@1990

@orpc/nest

npm i https://pkg.pr.new/@orpc/nest@1990

@orpc/next

npm i https://pkg.pr.new/@orpc/next@1990

@orpc/node

npm i https://pkg.pr.new/@orpc/node@1990

@orpc/openapi

npm i https://pkg.pr.new/@orpc/openapi@1990

@orpc/opentelemetry

npm i https://pkg.pr.new/@orpc/opentelemetry@1990

@orpc/pinia-colada

npm i https://pkg.pr.new/@orpc/pinia-colada@1990

@orpc/pino

npm i https://pkg.pr.new/@orpc/pino@1990

@orpc/publisher

npm i https://pkg.pr.new/@orpc/publisher@1990

@orpc/ratelimit

npm i https://pkg.pr.new/@orpc/ratelimit@1990

@orpc/server

npm i https://pkg.pr.new/@orpc/server@1990

@orpc/shared

npm i https://pkg.pr.new/@orpc/shared@1990

@orpc/swr

npm i https://pkg.pr.new/@orpc/swr@1990

@orpc/tanstack-query

npm i https://pkg.pr.new/@orpc/tanstack-query@1990

@orpc/trpc

npm i https://pkg.pr.new/@orpc/trpc@1990

@orpc/valibot

npm i https://pkg.pr.new/@orpc/valibot@1990

@orpc/zod

npm i https://pkg.pr.new/@orpc/zod@1990

commit: 414247e

[pullfrog]

✅ No new issues found.

Reviewed changes — single-commit mechanical migration of every @standardserver/* reference to @standard-server/* at ^0.9.0, reviewed across all 151 changed files (package manifests, lockfile, 100+ source/test imports, docs samples, Dependabot group, release-age excludes). No oRPC behavior changes: every hunk is an import/manifest/URL string swap.

• Scope migration — All @standardserver/* imports, dependencies, and lockfile entries moved to @standard-server/* at ^0.9.0; a case-insensitive repo-wide search (including the STANDARDSERVER_*/STANDARD_SERVER_* symbol-key strings) confirms the old scope no longer appears anywhere.
• Docs links — README links repointed to middleapi/standard-server; verified all four referenced anchors (#how-body-parsing-works, #body-types, #request-and-response-types, #event-stream-body) exist in the rendered README. Note: the new root README.md is a Git symlink to packages/core/README.md, but GitHub renders the target on the repo home page, so the anchors resolve.
• Upstream compatibility — The upstream v0.9.0 release notes confirm a rename-only release ("Rename to @standard-server/*"), matching the PR's compatibility claim; pnpm install --frozen-lockfile reports the lockfile in sync, and the mixed-scope event-metadata caveat is already documented in the PR description.
• Lockfile — One incidental re-resolution: @types/bun 1.4.0 → 1.4.1, driven by the latest specifier in playgrounds/bun/package.json. Expected side effect of the regeneration; no action needed.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}

[codspeed-hq]

Merging this PR will not alter performance

✅ 30 untouched benchmarks

---

_{Comparing dinwwwh:claude/standard-server-repo-migration-11fe77 (414247e) with main (89dc90d)}