Systems | Development | Analytics | API | Testing

When it comes to making HTTP requests in Node.js, developers are spoiled for choice: from the built-in and browser-familiar Fetch API to third-party libraries like Axios, Got, Superagent, Ky, and others. Navigating this diverse landscape can be a little daunting. This comprehensive guide aims to simplify your decision-making process by comparing the features and nuances of popular options, so you can select the ideal solution for your next project.

Jest and Vitest are two well-known JavaScript testing frameworks, each with its own strengths. Jest, created by Facebook, is especially popular for React applications. It provides a "zero-config" setup, built-in code coverage reporting, and snapshot testing, making it a complete solution for many JavaScript projects. Vitest, a newer framework in the Vite ecosystem, is known for its speed and lightweight design. Using Vite’s dev server, Vitest performs very well, especially in larger projects.

Error handling in Next.js is critical to providing a seamless experience to your users even when things go wrong. Without proper error management, users may get confused about what has happened and even leave your site. To avoid that, you must ensure that they receive informative feedback about errors and provide a way to recover from them. In this article, you'll see: Let's jump right in!

We're thrilled to announce the release of N|Solid 6, the latest version of our powerful tool designed to elevate your production Node.js applications and services. Packed with advanced features and enhancements, N|Solid 6 offers unparalleled insights and operational control, making it the go-to solution for monitoring, diagnosing, and securing your critical Node.js applications.

There are particular difficulties in getting NYC coverage from Node.js operating in Docker containers. This blog discusses the procedures needed to operate Node.js clusters in Docker and produce reliable code coverage reports.

AppSignal's Node.js package now offers out-of-the-box support for the AMQPlib package, enabling monitoring of inbound and outbound messages from popular Advanced Message Queuing Protocol (AMQP) brokers like RabbitMQ. In this article, we'll show you how to set up and use AppSignal to monitor your AMQP broker's performance.

Unit tests are essential to verify the behavior of small code units in a Node.js application. This leads to clearer design, fewer bugs, and better adherence to business requirements. That's why Test-Driven Development (TDD) and Behavior-Driven Development (BDD) have become so popular in the backend development community. In this tutorial, we'll dive into unit testing and understand why it's needed in your backend.

Welcome back to our exploration of Node.js' built-in test runner! In the previous article, we laid the groundwork for writing and running basic tests in your projects by exploring a few simple examples. In this installment, we'll dive into practical examples of how to use mocking, code coverage analysis, test hooks, and strategies for testing HTTP servers. These tools will help you write more comprehensive and reliable tests, ultimately leading to more robust Node.js applications. Let's get started!

The inclusion of a stable test runner in Node.js(version 18+) has generated significant debate in the community, given the abundance of established third-party testing frameworks. While its arrival naturally sparks comparisons to existing tools, this article won't focus on justifying its place in the ecosystem. Instead, we'll embark on a hands-on exploration of the test runner's core capabilities, from writing and executing tests to organization and customization features.

A well-known debate: tabs or spaces? Sure, we could set up a Google Form to collect this data, but where’s the fun in that? Let’s settle the debate, Kafka-style. We’ll use the new confluent-kafka-javascript client (not in general availability yet) to build an app that produces the current state of the vote counts to a Kafka topic and consumes from that same topic to surface them to a JavaScript frontend.