Hi,
In the past we had problems with deploying bundles to sandbox or production because they exceeded the 250MB limit when deployed. In the past this was mostly due to npm dependencies being in the dependencies instead of devDependencies, but as our project get bigger and as we're adding various static assets to the resources folder, it would be great to have an idea of how big our bundle is.
We understand that our code, assets and dependencies make up a part of the size, but there's also the Engine, included Themes blocks and maybe some other arc-provided things that add up the whole bundle, the sizes of which we don't know or how to measure.
We'd appreciate any bit of information on this part, so we can track it as we develop more blocks and add more assets to our repo.
BR,
Goran
Goran Gligorin
Hi Goran, as an update, latest PageBuilder CLI 2.3.0 includes a change that shows a warning if/when a bundle final size exceeds the "safe" limit (150mb bundle-code only) with the `npx fusion verify` command. It does stop the command execution and exit non-zero output so it's a good guard rail related with this idea.
Our engineering team is considering changing that warning behavior to always display the size of the bundle, potentially showing how close you are to the safe-limits in the same output. We'll keep this idea in Future consideration state until we ship that follow up version.
Hi Goran,
Thanks for submitting this idea.
It's an active conversation in our team to consider this capability into our CLI tool. We're looking into ways to create a way to see estimated bundle size.