Operations | Monitoring | ITSM | DevOps | Cloud

Over the past few weeks, we have been driving a cross-ecosystem effort to replace the “monkey-patching” that powers all JavaScript APM tools today with something built into the runtime. Here is why, how, and where it stands. This applies to server-side JavaScript only (Node.js, Bun, Deno, Cloudflare Workers). Browsers do not have diagnostics_channel and lack the async context propagation primitives needed to polyfill it.

Caching is critical to modern apps, helping you serve data more quickly and improve your app’s overall performance. Effective caches can result in better Core Web Vitals (CWV), improved search visibility, and a smoother user experience.

With AI writing more and more of our code, properly monitoring and debugging that code has become an increasingly critical part of the development workflow that can't be ignored. Luckily, we have more time than ever to implement the right tools to do so. Implementing a production-ready logging solution is easy to do, and provides you and your LLM Agents with a wealth of debugging information from your app, across users and environments.

When to use JavaScript or CSS in frontend projects is a matter of continued debate among many frontend developers. JavaScript is often the default choice for frontend development, as it offers a robust collection of libraries custom-made for creating advanced UI features, such as data-based visualizations or complex animations. But JavaScript also comes with tradeoffs, particularly when it comes to performance, accessibility, and code complexity.

Over the last couple of years, we've witnessed a remarkable shift in the JavaScript ecosystem, as many popular developer tools have been rewritten in systems programming languages like Rust, Go, and Zig. This transition has delivered dramatic performance improvements and other innovations that are reshaping how developers build JavaScript-backed applications.

Browser tracing has always been one of those things that feels invisible until it isn’t. When it works well, you get clear, actionable insights into how your app is performing in the wild. When it doesn’t, you’re left staring at noisy data, gaps in traces, and spans that don’t quite tell the story. Over the last few months, we’ve been chipping away at that problem.

When a page pauses for even a quarter-second users feel it, and many will tab away before the spinner stops. Front-end performance testing lets us spot those delays on our own machines instead of reading about them in support tickets. The browser runs JavaScript, layout, painting, and every user interaction on a single main thread. If one task takes too long, everything else queues up behind it.

There’s a lot of JavaScript developers these days not actually writing code. They whisper sweet prompts to our AI tools and hope for the best. Is it really any worse than copy-pasting from StackOverflow? Welcome to the era of vibe coding, where understanding your code is optional and “it works on my machine” has evolved into “the AI said it would work.”