In 2024, JavaScript is bigger than ever. The ecosystem is just as huge, and almost impossible to keep track of - so I've had a go at picking out 2024's most essential JS tools for you. In part 1 of this series, we reviewed runtimes and package managers, the foundational building blocks of your software project. So in part 2, we're analyzing the tools which form the walls and roof that give your software project its structure: frameworks and static site generators. For this installment of JS Toolbox 2024, we explore various frameworks & generators available in the JavaScript & TypeScript ecosystem, analyzing their strengths, weaknesses, and ideal use cases.

JavaScript remains the world's leading programming language, and with TypeScript now ascending to third most popular, JavaScript is bigger than ever! As a result, there's a bewildering range of tools on offer for JavaScript developers. And just as any durable structure needs a solid foundation, successful JavaScript projects rely heavily on starting with the right tools. This post, the first in our JS Toolbox 2024 series, explores the core pillars of the JavaScript & TypeScript ecosystem: Runtime environments, package management, and development servers.

From the first introduction of Core Web Vitals, Google has maintained that these user experience metrics will keep evolving. Since 2022, the Google team has been testing Interaction to Next Paint (INP), a new interactivity metric, and asking for feedback from the development community. Late in 2023, they announced that INP would replace FID as a Core Web Vital. The transition to INP is effective from March 2024.

Before the Raygun API limited release last year, we'd been consistently receiving requests for a public API for a long time, to provide a way for our customers to access their Raygun data programmatically. We're now proud to say we're providing a public API with a range of endpoints, but it took us a lot of planning and development to get here! In this post, I'd like to take you back to the beginning of development on our big API project. Specifically, I want to walk through the pivotal decisions we made around testing when we started development on the project, and how (and why) these have paid off.