Boom! Our latest release of the AppSignal for Node.js package now includes support for Next.js. The Next.js integration also includes end-to-end insights into application performance, as well as error tracking.

In today’s post, we’ll learn about Mnesia, see when you would use such a tool, and take a look at some of the pros and cons of using it. After covering the fundamentals of Mnesia, we’ll dive right into a sample application where we’ll build an Elixir application that uses Mnesia as its database. Let’s jump right in!

In today’s post, we’re going to demystify how the number of JavaScript dependencies grows while we’re working on a relatively simple project. Should you be worried about the number of dependencies? Keep in mind that this blog post is related to the Ride Down The JavaScript Dependency Hell blog post that was released a while back. We’ll show a “real-world” example of how a project’s dependencies can grow from zero to 13K.

Today’s release of Node.js integration supports PostgreSQL as well as all the consumers of the pg library.

We’re happy to announce that we’ve added a new feature which will make it easier for you to copy your trigger setup from one app to a new one. Anomaly detection triggers are a great way to get notified about unwanted events in your app. These anomalies are things like a high error rate, a lack of free disk space, or a high CPU usage. If your apps have a lot of the same requirements and infrastructure, you may have a lot of the same triggers across your apps.

Memory leaks are something every developer has to eventually face. They are common in most languages, even if the language automatically manages memory for you. Memory leaks can result in problems such as application slowdowns, crashes, high latency, and so on. In this blog post, we will look at what memory leaks are and how you can avoid them in your NodeJS application. Though this is more focused on NodeJS, it should generally apply to JavaScript and TypeScript as well.