refactor: use @react-native/assets-registry/registry

[jbroma]

Summary

based on the suggestion from @huntie, instead of using deep import from RN core, we can import @react-native/assets-registry/registry directly.

Test plan

• - testers work

[changeset-bot]

🦋 Changeset detected

Latest commit: 4bea110

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@callstack/repack	Patch
@callstack/repack-plugin-expo-modules	Patch
@callstack/repack-plugin-nativewind	Patch
@callstack/repack-plugin-reanimated	Patch
@callstack/repack-dev-server	Patch
@callstack/repack-init	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
repack-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 28, 2025 3:33pm

[jbroma]

upon further tests turns out it's not that simple - when we use deep import of AssetRegistry from core it results in a singleton registry module (since all imports of @react-native/assets-registry/registry are from within react-native)

if we however request the module from the context of project it will result in duplicate inclusion of assets registry, causing the module to be included twice in the build and not pointing to the same registry

[huntie]

@jbroma We probably want some abstraction then similar to rn-get-polyfills.js. I say "similar" in concept, not in exact design (this root file is somewhat horrible 😅). But it's an API design problem we'll have to take on over the coming months.

Making a note to discuss this at the Core Contributors Summit.

[jbroma]

@jbroma We probably want some abstraction then similar to rn-get-polyfills.js. I say "similar" in concept, not in exact design (this root file is somewhat horrible 😅). But it's an API design problem we'll have to take on over the coming months.

Making a note to discuss this at the Core Contributors Summit.

also not a big fan of root level entrypoints 😅

I've managed to almost get around this by rerouting all imports in the bundle to a virtual module from Re.Pack (kinda like a rn-get-polyfills.js) but then in the tests this fails because @react-native/assets-registry is not a peer dependency of Re.Pack 🙃 - it's a rather hacky solution to the problem.

I'll close this PR for now and we will tackle this in the future 👍