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.
We are very excited at NodeSource with the arrival of N|Solid Version 4.6.0. 🚀 In this release you will find a bunch of cool functionalities that will make your life as a developer and software team, easier. With even greater precision you will be able to monitor your Node.js projects better than ever!
Throughout the years I’ve created my fair share of native addons. The first ones were created by using the native C++ Node.js and v8 API’s. When NAN was created which made life much easier, especially in terms of maintenance, there was no question that I should move all my addons to use it. The years passed and Node-API was created and though it was on my radar and saw the benefits of using it, I never had the time to try it on my own modules.
NodeSource is excited to announce N|Solid v4.5.8 which contains the following changes: For detailed information on installing and using N|Solid, please refer to the N|Solid User Guide.
