Puppeteer is a powerful browser automation library for web scraping and integration testing. However, the asynchronous, real-time API leaves plenty of room for gotchas and antipatterns to arise. This article is part of a series, starting with Avoiding Puppeteer Antipatterns and Puppeteer in Node.js: Common Mistakes to Avoid. In this post, we'll add another dozen antipatterns to the list. There will be no overlap with previous installments, so you may wish to start with those.

As a developer supporting a growing business, you’ll likely spend a lot of time thinking about scaling. We live in a wonderful time to be solving scale problems. Computers are so fast and capable that many of the development decisions you make when writing backend systems won’t noticeably impact performance(until your app reaches an absolutely massive scale). If this weren’t the case, we’d all be writing web servers in C.

The npm createerror package is a helper that allows you to easily create custom error classes in Node.js. It provides a simple API to define and extend error classes with customizable properties and methods.

Almost every modern web browser includes a powerful suite of developer tools. In our previous blog-post we covered How to Measure Node.js server response time with N|Solid, read more 👉 HERE. The developer tools have a lot of capabilities, from inspecting the current HTML-CSS and Javascript code to inspecting the current ongoing network communication client-server.

As software developers, we constantly face new challenges in an ever-changing ecosystem. However, we must always remember the importance of addressing performance and security concerns, which remain at the top of our priority list. To ensure that our applications based on Node.js can meet our performance and scalability needs without compromising security or incurring costly infrastructure changes, we must be aware of the importance of network optimization in Node.js.

Node.js is a runtime environment that is reliant on the V8 JavaScript engine of Chrome that helps implement the JavaScript code on the server side. Node.js is not a framework or library. Because of its exceptional support of JavaScript and unique features, developers or business owners love Node.js a lot. Node.js helps in giving two-way constant communication between the client-side and server-side. And hence, Node.js breaks down the work pressure between the service provider and the client.

Node.js 12.x onwards introduced async stack traces. Async stack traces allow developers to view the call stack of asynchronous code, making it easier to trace and debug code issues. In this post, we’ll see how async stack traces work, how you can use them to debug code, and how to track them using AppSignal. Ready? Let's get going!

Node.js is an open-source server environment that is free to use. Built on a JavaScript V8 engine, Node.js runs on various platforms like Windows, Linux, Unix, Mac OS X, etc., and uses JavaScript on the server. Node.js is not a language, library, or framework but a runtime environment. Following are the 10 reasons to Choose Node.Js for Web Development.

For a few years now, Node.js has been widely recognized among developers. So, what is this latest buzz surrounding Node.js that we keep hearing about? Why is it so well-liked? You all must be curious to know the answers to these questions, right? Well, websites have undoubtedly grown significantly during the past 20 years, and Node.js has also experienced rapid expansion.

Chances are high that you've previously worked with Express, as it's been the go-to web framework for Node.js developers since its release in 2010. However, in recent years, newer web frameworks have emerged, and Express's development has slowed down significantly. Fastify is a relatively new player on the scene, but it's quickly gaining popularity due to its speed and unique features. If you're still using Express, you might wonder if it's worth switching to Fastify.