Bundling with Metro warns with "Require cycles are allowed, but can result in uninitialized values."

[kraenhansen]

We used to resolve these require cycles as part of producing a rollup bundle, but these will now surface as warnings when bundling with Metro.

We could probably revisit the decision to use a internal.ts to control the import order and instead focus on breaking the cycles:

realm-js/packages/realm/src/internal.ts

Line 21 in 1e1e48a

* We're following [the internal module pattern](https://medium.com/visual-development/how-to-fix-nasty-circular-dependency-issues-once-and-for-all-in-javascript-typescript-a04c987cf0de) to control of the order of code when bundled.

[sync-by-unito]

➤ PM Bot commented:

Jira ticket: RJS-2769