[LRUG] Troubleshoot asset pipeline with webpacker

[Ed James]

Hi LRUG

We have a custom internal NPM package for our front-end, which contains both CSS and VueJS assets. For months now our CircleCI build has been stable but we recently added a few more components to the package (benign stuff, simple).

We now have a build which consistently fails when compiling assets because of a RAM overflow i.e. we are suddenly exceeding our CircleCI RAM limit, which is 16GB!

We’ve run out of experiments and seems to have exhausted all avenues for fixing this. We are primarily a back-end team so we have no specialist webpacker/asset-pipeline knowledge in the team.

If anyone is willing to have a brief chat to run through any other potential gotchas/options, I would greatly appreciate it.

I did find this article particularly interesting, but our lack of asset-pipeline knowledge limit us from progressing down this route (which seems promising): https://rossta.net/blog/overpacking-a-common-webpacker-mistake.html

Thanks!


 	Ed James 
I will respect your spam <mailto:ed.james.spam at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20230523/5e90eb3c/attachment.htm>