If Sentry were a TV show, I think it would be Lassie. It’s your application’s best friend and everyone can understand it no matter what language they speak. Sentry gets help from the right people to make sure Timmy, I mean your application, is safe and sound. Over the past few months, we improved our Native SDK significantly. Most notably, we increased platform compatibility through a major rewrite from C++ to C and by switching to the CMake build system.

If you know anything about WebAssembly (WASM), it’s probably that WASM lets you execute code compiled from languages such as C, C++, Rust, or others in the browser at almost native speeds. You might be less familiar with the fact that WASM is not only an interesting technology in the browser, but also in other environments that require fast sandboxing. As such, WASM has found some popularity with edge computing and as a lightweight docker replacement for certain situations.

If you’re a JavaScript developer there’s a very good chance you’ve heard of or use Vercel. In the small chance you haven’t, Vercel is this awesome platform that makes building and deploying Jamstack frameworks like Next.js incredibly fast and easy. Next.js is gaining in popularity with 51k stars on GitHub and it’s one of the most trusted stacks in the JavaScript world these days.

For as long as we can remember, Sentry has had some version of CSV Exports. They’ve been limited only 1000 rows of results, which did the job for the most part. However, the more you used Sentry, the more we found that limit wasn’t good enough. What if I told you there was a way to get all your data in the exports in a single CSV? That’s right, no more DIY python scripts. No more manually piecing CSVs together. No more feature-request tickets.