chore: add funding link to published packages

[dinwwwh]

Every published package now carries a funding field pointing at the project's GitHub Sponsors page, so npm fund and the npm package pages surface a way to support the project.

Changes

• Added "funding": "https://github.com/sponsors/dinwwwh" to all 25 packages/*/package.json files, matching the link already used in .github/FUNDING.yml and the README's Sponsors section.
• The root package.json is private and was left unchanged.

Testing

Lint passes; the field is placed to satisfy the repo's jsonc/sort-keys ordering.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
orpc	Ready	Preview	Aug 4, 2026 1:15pm

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

@orpc/arktype

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

@orpc/bun

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

@orpc/client

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

@orpc/cloudflare

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

@orpc/contract

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

@orpc/experimental-effect

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

@orpc/evlog

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

@orpc/hibernation

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

@orpc/json-schema

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

@orpc/nest

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

@orpc/next

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

@orpc/openapi

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

@orpc/opentelemetry

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

@orpc/pinia-colada

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

@orpc/pino

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

@orpc/publisher

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

@orpc/ratelimit

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

@orpc/server

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

@orpc/shared

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

@orpc/swr

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

@orpc/tanstack-query

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

@orpc/trpc

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

@orpc/valibot

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

@orpc/zod

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

commit: 52f534b

[pullfrog]

✅ No new issues found.

Reviewed changes — a mechanical metadata update across every published package:

• Added "funding": "https://github.com/sponsors/dinwwwh" to all 25 packages/*/package.json files, placed alphabetically between license and homepage (satisfies the repo's jsonc/sort-keys ordering).

I verified the change end to end:

• The funding URL matches the existing references it claims to mirror — .github/FUNDING.yml (github: [dinwwwh]) and the README.md Sponsors link.
• Coverage is complete: all 25 non-private packages under packages/ receive the field, and there are no published packages elsewhere (every apps/* and playgrounds/* plus the root package.json are private: true, so leaving them unchanged is correct).
• Placement after license and before homepage keeps the jsonc/sort-keys ordering valid across all files.

No behavioral surface, no issues.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 25 untouched benchmarks

---

_{Comparing dinwwwh:claude/fund-link-packages-json-5c2d54 (52f534b) with main (f6bf880)¹}

Footnotes

1. No successful run was found on main (5961845) during the generation of this report, so f6bf880 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩