# Javascript
17 posts- From /users/123 to /users/:id: A Guide to Route Parametrizationdate: author: Sigrid Huemer
How Sentry's JS SDKs figure out your dynamic route names to make querying your issues easier.
- Formatting SQL in the Browser Using PEGdate: author: George Gritsouk
Writing a rudimentary SQL parser and formatter in JavaScript that handles Sentry's need to format invalid SQL and output into JSX.
- Better Code Rendering Through Virtualizationdate: author: Nicholas Deschenes
How we rebuilt Codecov's code renderer from the ground up to be faster and more efficient, utilizing virtualization.
- Perfectly Fitting Text to Container in Reactdate: author: George Gritsouk
Building a React component that automatically updates its font size to fill its parent element as fully as possible.
- Preact or Svelte? An Embedded Widget Use Casedate: author: Catherine Lee
Preact or Svelte, which framework is best for building an embedded user feedback widget?
- Mutation-testing our JavaScript SDKsdate: author: Lukas Stracke
Let's dive into mutation testing. In this post we talk about how mutation testing works, the state of it in JavaScript and we share our results of applying it to our JavaScript SDK repository
- How we fixed incorrect Codecov bundle size reportingdate: author: Nicholas Deschenes
How we resolved incorrect Codecov bundle size reporting when using GitHub Actions.
- Sentry JavaScript SDK v8 - A Retrospectivedate: author: Francesco Novy
This post will outline learnings the Sentry SDK team had from releasing v8 of the JavaScript SDKs.
- How we improved Performance Score accuracydate: author: Edward Gou
We're making updates to how Performance Scores are calculated in the Web Vitals module, which will bring them closer to what your users experience.
- How We Reduced Replay SDK Bundle Size by 35%date: author: Francesco Novy
An in-depth analysis of how we managed to cut the Session Replay SDK bundle size by 35%.
- Measuring Session Replay Overheaddate: author: Billy Vong
The best way to figure out how overhead impacts you is to measure it yourself. Follow along as we show you how we went about measuring overhead on Sentry and how you can measure it on your own applications.
- How we reduced CI time by 35% with Nx Cachingdate: author: Francesco Novy
Sentry is a very fast-moving company. In just one month we merged 165 pull requests from 19 authors and changed over 800 files, with a total of over 22,000 additions and almost 10,000 deletions. By updating to Lerna 6...
- How We Made JavaScript Stack Traces Awesomedate: author: Armin Ronacher
Sentry helps every developer diagnose, fix, and optimize the performance of their code, and we need to deliver high quality stack traces in order to do so. In this blog post, we want to explain why source maps are ins...
- Understanding the Performance Impact of Generated JavaScriptdate: author: Abhijeet Prasad
In the modern web, the JavaScript you write is often down-compiled using a compiler like Babel to make sure your JavaScript is compatible with older browsers or environments. In addition, if you are using TypeScript (...
- JavaScript SDK “Package Size is Massive” - So we reduced it by 29%date: author: Abhijeet Prasad
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 Java...
- How we trimmed the Sentry JavaScript SDK file size by 20%date: author: Abhijeet Prasad
SDKs naturally increase in size over time. After all, it does take more bytes to implement more features. This is not a big deal for most languages—the relative size of each new feature is small, and load times and st...
- Slow and Steady: Converting Sentry’s Entire Frontend to TypeScriptdate: author: Mark Story
Recently, Sentry converted 100% of its frontend React codebase from JavaScript to TypeScript. This year-long effort spanned over a dozen members of the engineering team, 1,100 files, and 95,000 lines of code. In this ...