NodeSource has been a part of the Node.js ecosystem since 2014, contributing to the open-source project, distributing binaries (over 100m annually!), providing expert Node Services, and building tooling (N|Solid) to support developers to make the best software leveraging Node.js. Every year, we look at the open-source projects we believe are the most interesting and will impact the ecosystem.
Installing Rookout on your Node.JS application is usually a breeze. Run `npm install`, add a line of code, and you are done. Yet, in some rare cases, we encounter more frustrating use cases. For example: When those tough situations arise, our customers often refer to this blog post we wrote years ago about deploying a Java Agent. So, if you are looking for an easy and portable way to deploy Node agents without changing your code, you’ll want to read this article.
Stack Overflow’s annual Developer Survey confirmed our experience; Node.js continues to grow its use across the globe due to its scalability and performance as well as its ability to integrate seamlessly with a wide range of technologies and databases make it an ideal technology for businesses of all sizes.
Node.js has seen meteoric growth in recent years, making it one of the most popular programming languages on the web. By combining Javascript on the front end with Node.js for backend development, JS developers can create powerful and scalable apps that offer benefits not found elsewhere.
NodeSource Node.js binary downloads keep increasing monthly, providing millions of users worldwide with the power of Node.js. This blog post gives us important insights into using Node.js across Linux environments and the Node.js community in general. Nodesource has been packaging and distributing Node.js for Linux environments for 9 years. Every major and minor release, as well as security updates. We’ve seen a massive increase in downloads every year.
Node is an open-source, cross-platform JavaScript run-time environment for developing server-side and networking applications. A peculiar feature of Node.js is its ability to process concurrent requests without delay. It uses an asynchronous programming method for doing so. Usually, when handling a request, the program sends this request to the computer’s file system. It then opens the requested file, reads it and then returns the content to the client.
Architecting a maintainable, readable, and reliable codebase is important not only for the people who will work on the code after you, but also for your own sanity. I’ve worked on dozens of production Node.js backend services and will share my experience of architecture pitfalls to avoid when building yours.
As unpleasant as they are, errors are crucial to software development. When developing an application, we usually don't have full control over the parties interacting with a program and its hosts (including operating system versions, processors, and network speed). It's important you have an error reporting system to diagnose errors and make errors human-readable. In this post, we'll first look at the two common types of errors.
The Node.js team recently announced the release of version 19. This has the following features: In this article, we will explore the major highlights of this release. We recommend downloading the latest Node.js 19 release to follow along. To verify your version of node: Let's get started!
Node.js 18 was released on the 19th of April this year. You can read more in the official blog post release or in the OpenJS Blog announcement. The community couldn't be more excited! If you want to lend a hand, we welcome your ideas or solutions contact us, or if you would like to help us continue supporting open source, you can contribute with an issue here.
