Streams are one of the oldest and most misunderstood concepts in Node.js, and that's not a developer's issue. The streams API in Node.js could be kind of hard to understand, which could lead to misunderstandings, wrong usages, and in worst scenarios, memory leaks, performance issues, or weird behavior in your application.
In this blog post, you can find a list and description of dependencies and other host Specs inside package.json. The dependencies in your project's package.json allow the project to install the versions of the modules it depends on. By running an install command inside a project, you can install all of the dependencies listed in the project's package.json, meaning they don't have to be (and rarely should be) bundled with the project itself.
In this chapter, we'll give you a kickstart introduction to effectively using package.json with Node.js and npm. The package.json file is core to the Node.js ecosystem and is a fundamental part of understanding and working with Node.js, npm, and even modern JavaScript. This file is used as a manifest, storing information about applications, modules, packages, and more.
It’s fair to say that the pandemic has not only wreaked havoc on how individuals live their daily lives but also on how they work. The global changes led to an immediate shift to remote working and unfortunately, not all enterprises were prepared for it. Companies did not have adequate time to prepare and allocate necessary security resources to ensure strong network and device protection for employees working remotely.
Today, npm is a cornerstone of modern web development, whether used exclusively with Node.js as a package manager or as a build tool for the front end. Understanding npm as a tool —particularly the core concepts— can be difficult for beginners. As such, we've written up this guide for getting a grasp on npm, especially for those who are entirely new to Node.js, npm, and the surrounding ecosystem.
TL; DR: Based on the APM benchmarks results is evident that one of the main performance problems for a Node.js application in a production environment is the usage of the very same applications in charge of monitoring the performance for the application itself. This article explains the reasons with an in-depth analysis to show why using most APMs in a Node.js application is that expensive performance-wise.
If you haven’t checked out the first two-part of our ‘Securing your Applications in Node.js’ series, click here and the second part here. This is a 3-part blog series on Node.js. This article aims to establish a Node.js security roadmap by addressing security challenges comprehensively and consistently for large infrastructures. Let’s begin! 🚀
If you haven’t checked out the first part of Securing your Applications in Node.js, click here. This is a 3-part blog series on Node.js. This article aims to establish a Node.js security roadmap by addressing security challenges comprehensively and consistently for large infrastructures. Let’s begin! 🚀
I know, right? NPM 8 was released just a couple of months ago and you’re looking for a blog post that summarizes all the changes and new stuff in the new version because you want to be ahead of the curve or simply don’t want your app to crash when upgrading. You googled but nothing relevant appeared; only a document from Github blog that refers to this issue on the NPM organization.
On the 26th anniversary of JavaScript, it's hard to fully measure the impact of this "open-source, cross-platform language for enterprise networks and the internet." It has transformed the landscape of computing by becoming the top language in development. Its community has grown significantly and taken a vital role in the evolution and, of course, support of JavaScript. It's a tremendous achievement!
