When in the production environment, it looks like webpack(?) is consuming a lot of memory for the build and it almost reaches the limit available for my server (currently reaching around 900mb of the Heroku free plan 512mb).
Is there any way we could extract the build process that this library runs in production mode so we could generate the views before starting the server?
Additionally we would have to check (or flag) for pre-built files on production mode.
I can tackle this one with some guidance.
When in the production environment, it looks like webpack(?) is consuming a lot of memory for the build and it almost reaches the limit available for my server (currently reaching around 900mb of the Heroku free plan 512mb).
Is there any way we could extract the build process that this library runs in production mode so we could generate the views before starting the server?
Additionally we would have to check (or flag) for pre-built files on production mode.
I can tackle this one with some guidance.