Jakub Romańczyk

It's still valid, hard to tell what's missing, haven't looked at that yet - we simply need to go through every flag and check if it makes sense in Re.Pack...

hi @sstatsuya we currently don't support decompressing downloaded scripts like that, this is something that would need to be added to the native module of Re.Pack since fetching of the...

> @jbroma I am having few queries before getting into the fix: > > 1. [`caller` Documentation says](https://re-pack.netlify.app/docs/api/repack/client/classes/ScriptManager#resolvescript) `Name of the calling script - it can be for example: name...

I suppose we could drop the caller altogether for the uniqueID, and rely on users specyfing [`output.uniqueName`](https://webpack.js.org/configuration/output/#outputuniquename) to avoid collisions. EDIT: From my understanding, the `scriptID` is unique within a...

@jefmoraes sorry for the late reply, I think what you're looking for are error boundaries. If the CDN fails then you could catch that with an error boundary and display...

this looks like something that is a good candidate for the docs

@vlack-coder that's a very good question! I'm not 100% sure about this, but you could call `invalidateScript` and try loading it again (for example by navigating back and forth so...

@HongQuang231 this is most likely due to dev-server listening only to IPv6 by default, try running `react-native start --host 127.0.0.1` to fix this. This is also something we fixed in...

I'm closing this one since the solution was provided and Re.Pack `4.0.0` is already released as stable and it includes the fix for this scenario. If you issue is still...

Hi @HongQuang231, is your `Xcode` configured properly, as stated in the docs? https://re-pack.netlify.app/docs/getting-started#4-configure-xcode