chore: upgrade standardserver to 0.8.3

[dinwwwh]

Upgrades all seven @standardserver/* packages from ^0.8.2 to ^0.8.3. The release's one code change is in @standardserver/node: absolute-form request targets such as GET http://host/path HTTP/1.1 now parse to /path instead of /http://host/path, so the Node adapter (and the Nest and Node static-file integrations built on it) routes such requests correctly behind proxies that forward absolute targets.

Changes

Only @standardserver/node changed behavior. @standardserver/core drops an implements ReadableWritablePair clause from the EventStreamDecoderStream declaration (types only, not referenced in oRPC), and the other five are republishes that keep the exact-version pins consistent. The minimumReleaseAgeExclude list swaps the aged-out 0.8.2 entries for 0.8.3 ones. No oRPC source or docs needed adapting.

Testing

• Full root vitest passes; pnpm type:check and eslint on the changed manifests are clean.
• pnpm install also rewrote the peer-suffix key of @tanstack/react-query-next-experimental (adds @babel/core to the next resolution). No version changed and this key has flipped before, so it is left as pnpm generated it.

[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@1985

@orpc/arktype

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

@orpc/bun

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

@orpc/client

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

@orpc/cloudflare

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

@orpc/contract

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

@orpc/experimental-effect

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

@orpc/evlog

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

@orpc/hibernation

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

@orpc/json-schema

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

@orpc/experimental-msw

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

@orpc/nest

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

@orpc/next

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

@orpc/node

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

@orpc/openapi

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

@orpc/opentelemetry

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

@orpc/pinia-colada

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

@orpc/pino

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

@orpc/publisher

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

@orpc/ratelimit

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

@orpc/server

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

@orpc/shared

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

@orpc/swr

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

@orpc/tanstack-query

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

@orpc/trpc

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

@orpc/valibot

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

@orpc/zod

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

commit: 6e21935

[pullfrog]

✅ No new issues found.

Reviewed changes — initial review of PR #1985 (commit 6e219351 vs base 6f5501f).

• @standardserver/* 0.8.2 → 0.8.3 across the workspace — all seven packages pinned to ^0.8.3 in the root manifest, 14 package manifests, the lockfile integrity/snapshot blocks, and the pnpm-workspace.yaml minimumReleaseAgeExclude list, with no stale 0.8.2 references left anywhere.
• Upstream behavior change contained to @standardserver/node — absolute-form request targets (GET http://host/path HTTP/1.1) now reduce to /path instead of /http://host/path. Verified against the merged upstream fix (middleapi/standardserver#85): origin-form paths pass through untouched and unparseable input keeps the old fallback, so oRPC's routing on request.url is unaffected — proxy-forwarded requests that used to 404 now route correctly. No engines floor change.
• Lockfile by-product is inert — the only other diff is the @tanstack/react-query-next-experimental@5.102.6 / next@16.3.3 peer-suffix keys gaining @babel/core@7.29.7; that package entry and its styled-jsx resolution already existed, so it's a resolution-key rewrite rather than a graph change.

Verified locally against the bumped deps: node adapter + static-file plugin + nest (260 tests) and server standard/fetch adapters + request plugins + evlog + hibernation (148 tests) all pass. CI test_matrix legs were green at review time.

  ^{｜ 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/standardserver-upgrade-0-8-3-bccd02 (6e21935) with main (6f5501f)}