fix(runtime): add Object.hasOwn polyfill for Hermes compatibility

[bheemreddy-samsara]

Description

Adds Object.hasOwn polyfill to the runtime package for Hermes compatibility.

Hermes (React Native's default JS engine) doesn't support Object.hasOwn (ES2022). This causes runtime errors when @vitest/expect v4.x initializes:

Object.hasOwn is not a function. (In 'Object.hasOwn(globalThis, MATCHERS_OBJECT)', 'Object.hasOwn' is undefined)

Related Issue

Fixes #51

Context

The error originates from @vitest/expect/dist/index.js:674:

if (!Object.hasOwn(globalThis, MATCHERS_OBJECT)) {

Since react-native-harness targets React Native (which uses Hermes by default) and depends on @vitest/expect v4.x, the polyfill belongs in the harness runtime rather than requiring every consumer to add it.

The polyfill is minimal and standards-compliant:

if (typeof Object.hasOwn !== 'function') {
  Object.hasOwn = (obj: object, prop: PropertyKey): boolean =>
    Object.prototype.hasOwnProperty.call(obj, prop);
}

Testing

• Tested on Android emulator with Hermes enabled
• Harness tests pass after adding this polyfill

References

• Hermes tracking issue: Feature request: Add Object.hasOwn (ES2022) facebook/hermes#1875
• MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn

[vercel]

@bheemreddy-samsara is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.