We’re thrilled to announce an exciting new release of N|Solid, bringing powerful updates designed to enhance Node.js performance and scalability. This release introduces two major features: These updates mark important advancements for Node.js developers and operations teams. The gRPC transition ensures a solid foundation for scaling and future-proofing your applications, while the AI-powered profiling tools empower you to fine-tune your performance with increased precision.

At NodeSource, we are always striving to enhance the resilience, scalability, and openness of our tooling. Recently, we took a significant step forward by adopting gRPC in N|Solid —a widely used open-source protocol for efficient communication between systems. This move represents a major shift in how we transmit data internally while ensuring seamless continuity for our users.

At NodeSource, we pride ourselves on delivering the best tools and open source support for Node.js users. Staying aligned with the latest releases is a key part of that commitment. With the latest Long-Term Support (LTS) release, Node.js 22 (codenamed "Jod"), we continue to ensure our users have access to reliable, secure, and up-to-date **Node.js binaries **through our NodeSource Binary Distributions.

If you want to run a SaaS app where your customers can each have one of their own domains pointing to your app, then you will encounter two problems: For example, let's say you wanted to provide a status page service hosted at yourapp.com that allows customers to set up their own domain (like status.acmecorp.com) to be served by your app. Let's dive into the solutions..

In the new age of Industry 4.0 the shopfloor is no longer an isolated environment. It’s the heartbeat of manufacturing operations, responsible for producing, monitoring, and refining goods. But since the lines blur between operational technology (OT) on the shopfloor and information technology (IT) in the enterprise, integrating these systems has become a formidable challenge.

Releasing a beta version of a Node.js package is a common practice when you want to share a new feature or a breaking change with testers or early adopters without affecting your stable users. Beta releases are tagged with a special version identifier (like 1.0.0-beta.0), making it clear that the version is pre-release and not production-ready. In this guide, we will cover the steps to release a beta version of your package using npm, ensuring a smooth and controlled release process.