Simon McLoughlin

@jevonearth sorry I might not have been clear. So Natively (on iOS using `JSContext`) you can only use a single static JS file. You can't pass in an NPM module...

@jevonearth Hi, I looked at this again as I badly needed the local-forging package, I have a solution using webpack thats working for that package, it would be great if...

I've created a fork and added this code to it, to make it easier for me to keep it updated. Would be great to have this automated and downloadable from...

@dsawali i'm currently only using the local-forging package. I can't use anything that has networking requests or anything like that in it

@dsawali I think the ideal solution would be to have a zip of all the native-mobile-compatible js files appear as a "asset" on each github release (see pic). Setting up...

@dsawali no that won't work. Looks like you've not read my previous comment. Native mobile JS doesn't have access to "window", as it's a headless JS implementation. It all has...

@roxaneletourneau apologies for only looking at this now. I've tested the latest version and yes it works great just copy / pasting it into my Swift project It would be...

@dsawali yes It was v17 that I used last time. I now have that working in my native iOS code. You can see if you download and unzip it, and...

I seem to have a workaround, but I don't know what impact it will have on trying to retrieve / check if images are cached, as doing so requires passing...

@dreampiggy Yes this would be great. In my case, I don't know ahead of time whether urls will be animated or not. So i'm just using SDAnimatedImageView everywhere I want...