Important: Buglesstack is in beta development. You can be one of our first users!

Login

Save days
debugging
pptr crashes

Speed up production debugging with instant visualisations of your puppeteer crashes.

Start debugging faster
jspptr-automation.js
async function queryGoogle() {
	const browser = await puppeteer.launch();
	const page = await browser.newPage();
	
	try {
		await page.goto('https://www.google.com/search?q=puppeteer');
		
		await page.waitForSelector('[name="q"]');
	}
	catch (error) {
		// Capture error information in Buglesstack
		await buglesstack.capture({ error, page });
		
		// Continue the error chain 
		throw error;
	}
}

Let's be honest.
You're tired of this:

the-problem

There is a better way ↓

easy

Install and debug

Identify the bug

Retrace the specific steps you took that led to encountering the bug.

Reduce debugging time

Solve the error the moment you find it.

Take a look

Check the page screenshot to know what was happening when it failed.

screenshot google

Debug the content

Buglesstack automatically saves the page's HTML content to be debugged. 

<h3 class="LC20lb MBeuO DKV0Md">
    Puppeteer | Puppeteer</h3>
<div
    class="notranslate HGLrXd NJjxre iUh30 ojE3Fb">
    <div class="q0vns"><span
            class="DDKf1c">
            <div class="eqA2re UnOTSe Vwoesf"
                aria-hidden="true">
                <img class="XNo5Ab"
                    src="data:image/png;base64,iVBO..."
                    style="height:26px;width:26px"
                    alt=""
                    data-csiid="WhwRZ5jtFa_W1sQP1eu9iA4_1"
                    data-atf="1">
            </div>
        </span>
        <div class="CA5RN">
            <div><span
                    class="VuuXrf">Puppeteer</span> 
            </div><span
                class="iG7WGe">·</span>
            <div class="byrV5b"
                style="overflow:auto">
                <cite
                    class="tjvcx GvPZzd cHaqb"
                    role="text">https://pptr.dev</cite>
            </div>
        </div>
    </div>
</div>
<div class="q0vns"><span
        class="DDKf1c">
        <div class="eqA2re UnOTSe"
            style="height:26px;width:26px">
        </div>
    </span>
    <div class="CA5RN">
        <div><span
                class="VuuXrf">Puppeteer</span>
        </div><span class="iG7WGe">·</span>
    </div>
</div>
Testimonials

What our clients are sharing

Discover the glowing feedback from our delighted customers worldwide

Ivan Muñoz

Ivan Muñoz

Founder of Afip SDK

We automate workflows on other pages and do not store our users' credentials, which makes it really hard to reproduce their bugs. With the discovery of Buglesstack for our tech stack, we stopped guessing what happened and started looking at what actually caused the bugs, saving invaluable time for our customers and helping to provide them with a smooth experience.
OrganicGram

OrganicGram

Fullstack Engineer

Being able to retrace the exact steps leading to a bug has been a lifesaver for us. It allows our team to quickly pinpoint where things go wrong in the automation process and resolve issues without guesswork.
Como en casa

Como en casa

Backend Engineer

Being able to save and analyze the HTML content of each page has been a crucial feature for us. It allows us to verify the accuracy of the data we scrape, ensuring that we capture all relevant information for the home chefs on our platform. This feature has streamlined our process and helped us maintain a high level of data quality.
Sam Mokhtary

Sam Mokhtary

Founder of Zero Tax Jobs

Buglesstack’s automatic screenshot feature has been invaluable, allowing us to quickly identify and resolve any issues that arise. This has significantly streamlined our workflow and reduced debugging time, making everything run smoother and more efficiently.
Dream Media

Dream Media

CTO

Having the ability to save and review the full HTML content of pages has completely transformed our debugging process. We no longer have to rely on guesswork when something goes wrong during automation. Instead, we can examine the exact data our scripts interact with, down to the smallest detail. This has been crucial in identifying discrepancies or issues in the scraping process that we might have otherwise missed.