Stack traces show us exactly where an exception occurred, but you can still be left wondering: What arguments or state caused the exception to occur?
If you can reproduce the issue locally with a debugger attached you’ll have access to these local variables, but with Sentry you can identify the exception location *without* needing to reproduce the issue locally. By including local variables with stack traces, Sentry events become much closer to the full debugging experience.
There are major package size benefits to reducing the amount of generated JavaScript your package is creating. As part of our larger Javascript SDK package reduction, we spent a considerable effort to minify as much of our code as possible. If you’re looking to do the same, here are six improvements to consider.
Developers started to notice just how big our JavaScript package was and yeah, we knew. We weren’t ignoring the issues; after all, we don’t want the Sentry package to be the cause of a slowdown. But to reduce our JavaScript SDK package size effectively we had to account for shipping new capabilities, like being able to manage the health of a release and performance monitoring, while maintaining a manageable bundle size. After all, new features == bigger package - usually.
The first part of a blog post series about bytecode transformations on Android, where we talk about different approaches to bytecode manipulation in Java as well as how to make it work with Android and the Android Gradle plugin.