You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building requires a very large spike in resource usage (Multi gigabytes of ram, CPU spike) compared to its normal running scenario. This makes it harder to provide good resource limits if we migrate to k8s
Reasons for the problem (I think):
Create react app requires you to provide environment variables at build time. As such, as there are two different versions of this app (4 if you count dev/prod split) those variables need to be provided at runtime. Because of the CRA limitation, we currently have to build the javascript during initial runtime in order to provide those variables, resulting in the above behaviour.
Potential solutions:
Fixing it isn't trivial, but these might be potential routes:
one build per environment (not great, we lose customisation post build and would need to store multiple images)
Outlining the problem:
Why this is bad:
Reasons for the problem (I think):
Create react app requires you to provide environment variables at build time. As such, as there are two different versions of this app (4 if you count dev/prod split) those variables need to be provided at runtime. Because of the CRA limitation, we currently have to build the javascript during initial runtime in order to provide those variables, resulting in the above behaviour.
Potential solutions:
Fixing it isn't trivial, but these might be potential routes:
The text was updated successfully, but these errors were encountered: