fix(scripts): preserve vendor method receivers - #907
Conversation
📝 WalkthroughWalkthrough
ChangesForwarding proxy behavior
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Caller
participant createProxy
participant createMethodProxy
participant NestedVendorObject
Caller->>createProxy: Access nested vendor method
createProxy->>createMethodProxy: Wrap method for its owner
Caller->>createMethodProxy: Invoke forwarded method
createMethodProxy->>NestedVendorObject: Reflect.apply(method, owner)
NestedVendorObject-->>createMethodProxy: Execute with correct this
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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) |
🤖 Harlan Agent Kit automated reviewThis was generated and posted by a robot, not Harlan's personal review. PASS · 95/100 confidence
Human merge decision still required. |
🔗 Linked issue
No linked issue. Found through Sentry issue NUXTSEO-SITE-17.
❓ Type of change
📚 Description
Forwarded vendor methods received the proxy as
this, which broke native receiver checks in Firefox. Method wrappers now call their owning raw object and cache nested proxies while retaining the existing void return contract.