(hi 👋 new here) So I was trying to work on this issue (#564) The linked doc does inform how to make puppeteer work by installing the repo version of chrome, but the problem is to launch that, we need access to the launch args, which are probably in the source of the package added here in this PR (#508), without which puppeteer launches its downloaded version anyway. Now possible solutions are • using GoogleChromeLabs/critters (no browser needed) instead of the above package, not sure if they are 1 to 1 in features though ◦ similar list of alternatives mentioned on the critters repo • symlink repo chrome to the path where puppeteer chromium is downloaded (messy 😬)

hey @User Welcome to SigNoz community 👋 and thanks for the detailed note @User is the lead maintainer for frontend parts in SigNoz. He should be able to help you out

Hi @User

ah my github username is

sadn1ck

I think critters is better than the

htmlcritical

as it is not using any browser

yeah that's what I think too, installing puppeteer everytime will also increase build times

can you please raise the pr for same... also do check the docker build is success-full and all the requirements are meet

sure, will do

awesome 😉

Thank you 😄

Ok but see is js lazy loaded ?

i think so? yes the scripts are deferred in the output

thank for raising the pr @User

yeah fixed the issue lol, missed the dupe keys