Dev Tools · 14h ago
EAS 4 KiB limit forces workaround for Expo multi-environment configs
Expo's EAS build service caps file-type environment variables at 4 KiB, breaking apps that use large config files like Amplify's amplify_outputs.json. A developer solved this by committing separate output files per environment and using an eas-build-pre-install hook to copy the correct one. The workaround is essential for mobile apps that must bake backend configuration into builds at commit time.
Meridian48 take
The 4 KiB limit is a sharp edge in EAS that will catch more developers as Amplify Gen 2 and similar tools produce ever-larger config files.
Read the full reporting
One backend, three environments: the 4 KiB limit that redesigned my EAS setup →
DEV Community
expo-easamplify-config