During the last few months, we've been working hard on improving our Node.js integration. We've released loads of quality fixes and improvements to our diagnose command, configuration, and general package structure. Today, we'd like to highlight some of the enhancements and fixes that we've recently released.

Modern software projects are mostly composed of open source code. The question of who really controls this code, and is responsible for detecting and fixing software supply chain security issues, became a significant source of concern after the discovery of the Log4Shell vulnerability.

In this tutorial, we will go through a working example of a Node.js application auto-instrumented with OpenTelemetry. In our example we’ll use Express, the popular Node.js web application framework. Our example application is based on two locally hosted services sending data to each other. We will instrument this application with OpenTelemetry’s Node.js client library to generate trace data and send it to an OpenTelemetry Collector.

Great search and aggregation features can make a big difference to your application. Read on to see how to use OpenSearch with your NodeJS.

Node.js applications are those that are created on the Node.js platform, which is an event-driven I/O server-side JavaScript environment based on Google Chrome's V8 engine. Since both the server-side and client-side are written in JavaScript, Node.js allows for easier and faster code implementation, as well as processing requests quickly and simultaneously. This is especially useful for developing real-time applications, such as chat and streaming.

When your application starts to grow, one of the essential factors to consider while scaling is memory management. Poor memory management leads to memory leaks, thus affecting application performance. When the performance degrades, it will directly affect the business. So, it is essential to look out for and fix memory leaks in time. This blog post will look at what memory leaks are and how to avoid them in Node.js applications. Feel free to navigate the post using these links.

Built on the V8 JavaScript engine of Chrome, Node.js is a very lightweight, open-source framework with minimum modules. And since it is an asynchronous system by default, it is faster than most other frameworks. DevOps still need Node.js monitoring to ensure performance better than other frameworks. In order to understand how relevant Node.js still is, note that PayPal, Reddit, LinkedIn, Amazon, Netflix and other high-use, high-visibility service providers use the framework.

NestJS is fast becoming the de facto framework for NodeJS projects. Unlike older frameworks, NestJS was built with TypeScript, which has become commonplace in the JavaScript community. Frameworks like NestJS seem to be preferred by teams that adopt TypeScript. NestJS supports building APIs in REST and GraphQL. The goal of this tutorial is to show how you can add unit and integration tests to a NestJS GraphQL project and automate the testing process with CircleCI.

AWS S3 is a cloud storage service that saves data as an object associated with a key. Objects are like files and keys are like filenames. Objects are stored in a bucket. We will be auto-generating our object keys while uploading. In a free tier account, you get 5GB of free cloud storage with AWS S3. Note: This tutorial is made for AWS S3 but works as well with S3 compatible providers like Wasabi.com

CircleCI orbs are reusable packages of YAML configuration that condense repeated pieces of config into a single line of code. Since its launch in 2018, the CircleCI orbs registry has been used by developers, development teams, and by companies who want to help developers integrate their services seamlessly into continuous integration pipelines. In this tutorial, we will show how to use CircleCI orbs to continuously deploy a Node.js application to Heroku, one of the most popular hosting platforms.