Bugpilot v2 is here!

React Server Components (RSC) have fundamentally transformed how we build apps with React. Having React components run on the server means transferring less JS to the browser, accelerating the initial loading time, and enhancing the overall user experience. For us at Bugpilot, this change told us that solely capturing errors on the client side was no longer sufficient. Therefore, we decided to focus on the most popular React framework with approximately 5M weekly downloads (via npm) – Next.js.

What's changed in Bugpilot?

We made it super easy to get started with Bugpilot. Run npx @bugpilot/wizard and follow the installation guide. That's it. There is no need to change your code. We also made an effort to make sure we don't slow down your app, so there are no production dependencies.

Server-side errors

Bugpilot is now a full-stack error monitoring platform. On top of client-side errors, Bugpilot now captures unhandled errors in your server and edge environments. Any errors thrown in your pages, layouts, components, server actions and middleware will be caught and reported to you. You'll get a stack trace, session replays, user and environment info, and additional information about each error's first and last occurrence.

User-friendly error pages

We understand how errors can be troublesome for users. That's why we've included user-friendly error pages that help you handle these situations more gracefully. You can easily integrate them into your app simply by importing them in your error.tsx of your Next.js app.

Customize the way your users report bugs

Not all errors stem from your code. We recently discovered an infinite loading issue with a third-party tool that we are using, thanks to a bug report from one of our users. Now, you can wrap any component with our <WidgetTrigger> and customize how your users will trigger the bug reporting flow.

Bugpilot is now built with Next.js

For you, this means faster load time and an overall better experience. All of your errors are on the Error Logs page, while the bugs reported by your users are on the User Reports page. We made this decision because we wanted to use our error monitoring tool on our app.

What's next for Bugpilot?

We'll be working on capturing errors in route handlers.

Pages Router

Since the App Router is a relatively new addition, we understand that some of you might have applications in production using the Pages Router and might not be ready to switch. If this applies to you, please let us know so our team can prioritize the Pages Router support accordingly.

Will you support other frameworks?

Maybe in the future. Currently, there is a significant difference in usage between Next.js and other React-based frameworks. We aim to build the best possible error monitoring tool for Next.js before moving on to other technologies.
We are super excited for you to try Bugpilot and give us your feedback.
Simone & Krste,
Co-founders of Bugpilot