refactor: type clean up - #822
Conversation
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (124)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📦 Bundle Size
All bundles (14)
📦 Runtime Dependencies✅ No runtime dependency changes All packages (10)
Skipped optional dependencies (114)
Production dependencies only. Peer dependencies and Unhead workspace packages are excluded. Skipped optional dependencies are unavailable on the CI platform. ⚡ Performance (directional)✅ No significant change (within CI noise) All benchmarks (14)
Baseline: main @ d9b3d2a · 2026-07-26 · gzipped is the headline size metric · perf is directional (shared-runner, gated) |
# Conflicts: # packages/react/src/context.ts # packages/schema-org/src/core/define.ts # packages/unhead/src/legacy/index.ts
# Conflicts: # bench/perf-ci.mjs # packages/angular/src/composables.ts # packages/react/src/composables.ts # packages/solid-js/src/composables.ts # packages/svelte/src/composables.ts # packages/unhead/src/legacy/index.ts # packages/unhead/src/scripts/types.ts # packages/unhead/src/scripts/useScript.ts # packages/unhead/test/unit/scripts/use.test.ts # packages/vue/src/scripts/useScript.ts
# Conflicts: # packages/react/src/client.ts # packages/react/src/helmet.ts # packages/react/src/server.ts # packages/react/src/stream/client.ts # packages/react/src/stream/server.ts # packages/react/test/public-types.test.ts # packages/schema-org/src/core/graph.ts # packages/schema-org/src/core/resolve.ts # packages/schema-org/src/nodes/Event/index.ts # packages/schema-org/src/nodes/Offer/index.ts # packages/schema-org/src/nodes/Organization/index.ts # packages/schema-org/src/nodes/Video/index.test.ts # packages/schema-org/src/nodes/Video/index.ts # packages/schema-org/src/nodes/WebPage/index.test.ts # packages/schema-org/src/nodes/WebPage/index.ts # packages/schema-org/src/plugin.ts # packages/schema-org/src/react.ts # packages/schema-org/src/runtime.ts # packages/schema-org/src/solid-js.ts # packages/schema-org/src/svelte.ts # packages/schema-org/src/vue/runtime/composables.ts # packages/schema-org/test/types.test.ts # packages/schema-org/test/vue/vue.test.ts # packages/unhead/src/plugins/flatMeta.ts # packages/unhead/src/plugins/inferSeoMetaPlugin.ts # packages/unhead/src/plugins/minify.ts # packages/unhead/src/plugins/safe.ts # packages/unhead/src/plugins/validate.ts # packages/unhead/test/unit/types.test.ts
🤖 Harlan Agent Kit automated reviewThis was generated and posted by a robot, not Harlan's personal review. PASS · 90/100 confidence
Human merge decision still required. |
🔗 Linked issue
N/A
❓ Type of change
📚 Description
Threads
Input/RenderResultgenerics throughUnhead,HeadPluginand the head hooks sohead.render()is typed per environment (SSRHeadPayloadfor server heads) instead ofany, with each framework package (vue, react, solid, svelte, angular) preserving the generics through its owncreateHead/context layer.Loose surfaces tighten alongside:
PropResolvertakesunknowninstead ofany,HeadEntry.optionsderives fromHeadEntryOptionsinstead of a hand-rolled copy, and the legacycreateServerHeadgains overloads that keepdisableDefaultsinference. Type erasure now happens at single documented boundaries (for exampletoUnheadContextValuein the React context) rather than scattered casts. New public-type specs in the angular and eslint-plugin packages lock the exported type surface.