Repository navigation
Conversation
Drop the `experimental-` prefix from the Effect integration's package name and update the root devDependency, lockfile, READMEs, docs and JSDoc examples to match. The v1 migration guide now lists the rename alongside the other promoted packages. BREAKING CHANGE: `@orpc/experimental-effect` is renamed to `@orpc/effect`. Update your dependency and imports to the new package name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XRN3JRAKNk8bhHBEHAjjSJ
|
Macroscope skipped reviewing this pull request. Per-review cost limit exceeded (workspace setting). This review would cost an estimated $18.81, which exceeds your per-review limit of $10.00. The top 3 files driving up this estimate:
Tip To get this pull request reviewed, you can:
|
ApprovabilityVerdict: Needs Human Approval Macroscope's review found this PR requires human approval — The PR consistently renames the Effect integration package and updates its documentation and workspace metadata without changing implementation logic. However, removing @orpc/experimental-effect is a breaking public package change for existing consumers and merits human review of the release and migration plan. Needs human approval because:
Review your spending limits in Billing settings, or comment |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — complete rename of the Effect integration package from @orpc/experimental-effect to @orpc/effect.
- Package identity —
packages/effect/package.jsonname→@orpc/effect(version unchanged at2.0.0-beta.45); rootpackage.jsondevDependency andpnpm-lock.yamlroot importer key moved (lockfile importers are path-keyed, so only the root key changes — correct). - Source JSDoc — two
WithEffectContext@exampleimport lines inpackages/effect/src/context.ts. - Docs —
integrations/effect.mdx(install command keeps the@betaconvention; all imports updated),api-reference.mdxpackage row, and the intended@orpc/experimental-effect→@orpc/effectrow inmigrations/from-v1.mdx. - READMEs —
packages/effect/README.mdnpm link + weekly-downloads badge, plus the framework-integration table reflowed across the root and 29 package READMEs (the old name was the widest first-column cell).
I verified the rename is complete: grep experimental-effect across the repo returns only the migration-table row, and no package.json, tsconfig, workflow, playground, or test still references the old name. This is a mechanical rename with no behavioral surface.
deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏
Merging this PR will not alter performance1 warning
Comparing Footnotes
|
More templates
@orpc/ai-sdk
@orpc/arktype
@orpc/bun
@orpc/client
@orpc/cloudflare
@orpc/contract
@orpc/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: |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
orpc | f15b438 | Commit Preview URL Branch Preview URL |
Oct 23 2026, 02:38 PM |

Drops the
experimental-prefix from the Effect integration.packages/effectis now published as@orpc/effect. This follows the@orpc/mswrename in #2258 and the v2 promotions in #1593.Changes
packages/effect/package.json: renamed to@orpc/effect.package.jsondevDependency andpnpm-lock.yaml: lockfile regenerated with pnpm 12.4.2. The only change is the moved importer entry.README.mdand all 29packages/*/README.mdfiles. The old name was the widest cell in the first column, so the formatter narrowed the whole column. That's why each README shows about 15 changed lines.packages/effect/README.md: npm link and weekly-downloads badge.packages/effect/src/context.ts: JSDoc import examples.apps/content/docs/integrations/effect.mdx: install command (npm install @orpc/effect@beta effect, keeping the@betaconvention every v2 page uses) and all imports.apps/content/docs/api-reference.mdx: package row.apps/content/docs/migrations/from-v1.mdx: adds@orpc/experimental-effect→@orpc/effectto the renamed-packages table.The only "experimental" wording about Effect in the docs was the package name itself. The only remaining
experimental-effectreference is the migration-table row.Pre-stable fixes
Landed on main:
effect/wraprework: feat(effect): enhance effect/wrap with discriminated options and context passing #2262onExcessPropertyin the JSON Schema converter example #2259, docs(effect): fix Effect v4 samples and add runtime notes #2260Not on main yet, with no open PR:
toStandardSchemastill returnsSchema<Encoded, Type>for.output(), so handlers return the encoded form.toStandardSchemahardeningpeerDependencies.effectis still>=4.0.0, while tests run against^4.0.5.The package is still on
2.0.0-beta, so the stability promise starts at the 2.0.0 release, not at this merge. Whether these must land before this PR merges is the maintainer's call.npm registry steps (maintainer only, not run)
Current state:
@orpc/effectis unclaimed (404).@orpc/experimental-effecthaslatest: 1.14.11andbeta: 2.0.0-beta.45. 1.14.11 is deprecated as "Published by mistake (contains v2 code). Please upgrade to 1.14.12 or v2." But 1.14.12 doesn't exist, and 1.14.11 pins@orpc/server,@orpc/contract,@orpc/sharedand@orpc/json-schemaat exactly1.14.11.release.yamlpublishes through trusted publishing (OIDC), which can only be set up on a package that already exists. For@orpc/msw, the first versions were published by hand, then2.0.0-beta.45came from the workflow. Same here, from this branch:middleapi/orpc,release.yaml) in the@orpc/effectsettings on npmjs.com. As with@orpc/msw, the first publish also setslatest.@orpc/effectpublish, deprecate every version of the old name. This also replaces the 1.14.11 message that points to the nonexistent 1.14.12:npm deprecate @orpc/experimental-effect "Renamed to @orpc/effect"lateston the old name still points to the broken 1.14.11, so a plainnpm install @orpc/experimental-effectinstalls it, now with the rename warning. To send plain installs to the last v2 build instead:Test plan
pnpm lintpnpm type:checkpnpm test: 289 files and 4044 tests passed, 72 skipped; Bun 142/0; Cloudflare 74/74pnpm docs:validate: 0 JSDoc errors across 231 symbols,blume validate --strictfound no broken linkspnpm --filter @orpc/effect prepackbuilds, andnpm pack --dry-runreports@orpc/effect@2.0.0-beta.45Generated by Claude Code