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!
Javascript is here to stay! And the server-side Node.js project is no different 💚. This year marks the 12th (Dec 4, 2009) anniversary of the birth of Node.js, and although it may seem incredible, Javascript has been around for 25 years and the web respectively 32 years. The ecosystem of Node.js is mature and supported by an active community of library developers and authors. Being so popular, it also becomes an exciting challenge for crackers.
A bug on your Node.js application can mean many things: In other words, a bug on your Node.js application can mean a lot of different things depending on the industry you are working in. Some industries can't afford 5 minutes down; others can afford weeks down. Even more important, the software - correctly working - can impact lives.
NodeSource from the beginning was created with a great commitment for the developers’ community, that is why it has provided documentation for using the NodeSource Node.js Binary Distributions via.rpm, .deb as well as their setup and support scripts. We are also aware that as a start-up you want ‘Enterprise-grade’ at a startup price, this is why we extend our product to small and medium-sized companies, startups, and non-profit organizations with N|Solid SaaS.
