App with large data files > Packager not happy about expo-cli HOT 10 CLOSED

200Mb sounds like a lot and you're right. My files are 20Mb and they're not assets, they're part of the code :/ I dont know if that changes anything?

from expo-cli.

Hey, thanks for the well written question. I've pinged a couple people on the team who might have ideas about this.

from expo-cli.

I think the remote API approach may be the best one here given that it'll be in your control. You could also address other things -- like whether you need all the data upfront and whether your client and server can communicate through time to transmit only required chunks as needed. One quick thing you could try is splitting up the single file and using multiple assets -- I've had assets work for 200mb total of images for example where each file was about 3-8mb.

from expo-cli.

+1 to the remote API. This way when you publish a new update to your app, people don't need to redownload all the data as well.

from expo-cli.

I prefer having all the data in the app as it's cheaper for me ;) and most importantly it's less breaking points. Trying to keep the complexity down.

I seem to have found the limit but I'm not sure. I can load all the data if I divide it in files of maximum 2Mb and then import it all back one structure. In this case, if 2Mb is the limit, the complexity is just in the script that creates the database and I'm fine with this.

So there's something to look into, what do you think? I dont know if your time is worth checking that issue since not many of us end up in this situation but at least you know there's something going on there.

Thanks for coming back to me on this one.

from expo-cli.

A 200MB over-the-air update will likely lead to unreliable and potentially costly (ex: data plans) updates for your users. To strike a balance, we (Expo) might need to put a cap of ~10MB on OTA updates and leave bundled assets in standalone apps have no cap -- this seems respectful to users who can see the total app size in the App Store / Google Play and switch to Wi-Fi if they need to.

from expo-cli.

I found I was able to get around this issue in expo v24 by adding a line in my .babelrc like "ignore": [ "*.json" ]. But this workaround is no longer effective in expo v25. Seems like it's probably an issue with the way expo interacts with the metro bundler, but hard to tell. See facebook/metro#123 or facebook/metro#111 for instance.

from expo-cli.

Any news on this? The issue with large files has been around for quite some time and
even with bable v7 (where ignore is supposed to work again) does not work for me.

from expo-cli.

cc @fson

from expo-cli.

This is an upstream Metro bundler issue. Nothing we can do in expo-cli.

from expo-cli.