Kræn Hansen

As we publish releases here on GitHub a solution that might work for you is simply to watch this repository. I'm curious why you see a need for this, since...

I've noticed this PR says > This feature is experimental and unsupported. We will document and announce this for general consumption once it's stable. Are there plans to stabilise this?...

Loss of data is of course something we take very seriously, so we're very invested in getting to the bottom of an issue like this. We do however need a...

@elle-j and I looked further into this last week and realized: 1. `bson@6` is relying soly on exports conditions to expose its React Native bundle: https://github.com/mongodb/js-bson/blob/c58d1e213714c99bbb09d0f91a3c9199e43710dd/package.json#L90. This problematic, because Metro...

This draft PR is somewhat related: https://github.com/realm/realm-js/pull/5369

We agree an error like this should signaled differently than calling `console.error`: 1. Calling `onError` would be difficult, because that function takes the active sync session, but at this point...

``` npm ERR! Missing: @types/[email protected] from lock file npm ERR! Missing: [email protected] from lock file ``` You'll need to run `npm install` and commit the changes to the lock file...

It looks like Metro is picking up our Node.js entrypoint when bundling. Could you share your metro configuration? For one thing, wondering if you have `unstable_enablePackageExports` enabled.

Thanks for creating the issue. We do test with the new arch enabled: https://github.com/realm/realm-js/blob/a5e797c802a971bdd1112b95ef8be215186c1f9b/integration-tests/environments/react-native-test-app/package.json#L105-L108 I've just rebased my branch upgrading our test app to 0.74.0 🤞 https://github.com/realm/realm-js/pull/6636

I'm reproducing https://github.com/react-native-maps/react-native-maps/issues/5042 when running our React Native 0.74.0 branch locally 👀 and the stack doesn't seem related to Realm.