---
title: "#node articles | Hashnode"
description: "Explore 734 articles tagged #node on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/node"
---

Tag

# #node

734 posts · 110 followers

[Dan Holloran](https://hashnode.com/@grimicorn) · [10h ago](https://hashnode.com/posts/nuxt-server-write-server-routes-today-that-still-run-on-nuxt-5/6afc372482b7d385f052d382)

### [nuxt/server: Write Server Routes Today That Still Run on Nuxt 5](https://grimicorn.hashnode.dev/nuxt-server-write-server-routes-today-that-still-run-on-nuxt-5?utm_source=hashnode&utm_medium=feed)

Every Nuxt app with a server/ directory has a quiet dependency problem. Your API routes call defineEventHandler, getQuery, and readBody, and those come from h3. Your modules import types from nitropac

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/nuxt-server-write-server-routes-today-that-still-run-on-nuxt-5?utm_source=hashnode&utm_medium=feed)

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [14h ago](https://hashnode.com/posts/pm2-tutorial-keep-your-node-js-app-running-for-good/6afbf721d0e9e9fe45080485)

### [PM2 Tutorial: Keep Your Node.js App Running for Good](https://practicaldevblog.hashnode.dev/pm2-tutorial-keep-your-node-js-app-running-for-good?utm_source=hashnode&utm_medium=feed)

Quick answer PM2 is a process manager for Node.js: it starts your app in the background, restarts it when it crashes, and keeps it running after you log out. This post runs a small order-status API un

8 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/pm2-tutorial-keep-your-node-js-app-running-for-good?utm_source=hashnode&utm_medium=feed)

[Dan Holloran](https://hashnode.com/@grimicorn) · [3d ago](https://hashnode.com/posts/node-sqlite-the-database-that-already-ships-with-node/6af84287365f08bbb4596ea3)

### [node:sqlite: The Database That Already Ships With Node](https://grimicorn.hashnode.dev/node-sqlite-the-database-that-already-ships-with-node?utm_source=hashnode&utm_medium=feed)

Every small Node project hits the same fork in the road. You need to persist something: a queue of jobs, a cache of API responses, the bookmarks for a CLI tool. A JSON file feels too fragile, Postgres

5 min read · [grimicorn.hashnode.dev](https://grimicorn.hashnode.dev/node-sqlite-the-database-that-already-ships-with-node?utm_source=hashnode&utm_medium=feed)

[Abdus Salam](https://hashnode.com/@aheadkit) · [5d ago](https://hashnode.com/posts/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds/6af55e573fc20b6976a473b4)

### [What Raising the bcrypt Cost Factor Actually Costs in Milliseconds](https://aheadkit.hashnode.dev/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds?utm_source=hashnode&utm_medium=feed)

Somewhere in your codebase there is a line that looks like this: const hash = await bcrypt.hash(password, 10); That 10 is the cost factor, and most tutorials tell you to set it to 10, or 12, and move

5 min read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/what-raising-the-bcrypt-cost-factor-actually-costs-in-milliseconds/6af55e573fc20b6976a473b4)

[Abdus Salam](https://hashnode.com/@aheadkit) · [5d ago](https://hashnode.com/posts/reading-a-large-file-with-streams-instead-of-readfilesync-in-node-js/6af55dd674ce2f39ff0f8b7d)

### [Reading a Large File With Streams Instead of readFileSync in Node.js](https://aheadkit.hashnode.dev/reading-a-large-file-with-streams-instead-of-readfilesync-in-node-js?utm_source=hashnode&utm_medium=feed)

A server I work on writes request logs. One day I needed to count lines in a day's worth — about 8 million lines, 505 MB on disk — and my first instinct was the obvious one: const data = fs.readFileSy

5 min read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/reading-a-large-file-with-streams-instead-of-readfilesync-in-node-js?utm_source=hashnode&utm_medium=feed)

[Abdus Salam](https://hashnode.com/@aheadkit) · [5d ago](https://hashnode.com/posts/structuredclone-vs-json-parse-json-stringify-for-deep-copying-in-node-js/6af55d3803f632951bc1deb9)

### [structuredClone vs JSON.parse(JSON.stringify()) for Deep Copying in Node.js](https://aheadkit.hashnode.dev/structuredclone-vs-json-parse-json-stringify-for-deep-copying-in-node-js?utm_source=hashnode&utm_medium=feed)

I copied a config object the way everyone does it. JSON.parse(JSON.stringify(obj)), one line, done. The object had a Date in it and a Map. The copy came back, the code ran, and half an hour later some

5 min read · [aheadkit.hashnode.dev](https://aheadkit.hashnode.dev/structuredclone-vs-json-parse-json-stringify-for-deep-copying-in-node-js?utm_source=hashnode&utm_medium=feed)

[Waqas Shahid](https://hashnode.com/@practicaldevblog) · [6d ago](https://hashnode.com/posts/fastify-a-fast-node-api-without-the-ceremony/6af3f30cfadf5a623bca7641)

### [Fastify: A Fast Node API Without the Ceremony](https://practicaldevblog.hashnode.dev/fastify-a-fast-node-api-without-the-ceremony?utm_source=hashnode&utm_medium=feed)

Picture a small shop that takes orders through a web page. A customer fills in a form, the browser sends the order as JSON, and a Node server has to check the fields, save the order, and answer with t

8 min read · [practicaldevblog.hashnode.dev](https://practicaldevblog.hashnode.dev/fastify-a-fast-node-api-without-the-ceremony?utm_source=hashnode&utm_medium=feed)

[Sohail Khan](https://hashnode.com/@msohailkhandev) · [Nov 10](https://hashnode.com/posts/your-api-does-not-need-more-logs-it-needs-one-error-shape/6af2f01eaf8577ecd8257580)

### [Your API Does Not Need More Logs. It Needs One Error Shape.](https://msohailkhandev.hashnode.dev/your-api-does-not-need-more-logs-it-needs-one-error-shape?utm_source=hashnode&utm_medium=feed)

Your API does not need more logs. It needs one error shape. A client I worked with kept breaking every time an endpoint failed. One error came back as plain text, the next as an HTML page, the next as

4 min read · [msohailkhandev.hashnode.dev](https://msohailkhandev.hashnode.dev/your-api-does-not-need-more-logs-it-needs-one-error-shape?utm_source=hashnode&utm_medium=feed)

[Muhammad Afzal Kalwar](https://hashnode.com/@mafzalkalwardev) · [Nov 10](https://hashnode.com/posts/building-mailforge-a-self-hosted-email-desk-for-verification-campaigns-and-a-unified-inbox/6af2ede1569e7935f96ce291)

### [Building MailForge: a Self-Hosted Email Desk for Verification, Campaigns and a Unified Inbox](https://mafzalkalwardev.hashnode.dev/building-mailforge-a-self-hosted-email-desk-for-verification-campaigns-and-a-unified-inbox?utm_source=hashnode&utm_medium=feed)

Run list checks over SMTP, send from accounts you add, and read replies on a machine you control — Node.js, Go and MongoDB, MIT licensed.

7 min read · [mafzalkalwardev.hashnode.dev](https://mafzalkalwardev.hashnode.dev/building-mailforge-a-self-hosted-email-desk-for-verification-campaigns-and-a-unified-inbox?utm_source=hashnode&utm_medium=feed)

[Mahir Faysal](https://hashnode.com/@mfaysaldev) · [Nov 9](https://hashnode.com/posts/javascript-promise-all-vs-allsettled-vs-race/6af1f9533eced284c7b93dab)

### [Promise.all vs Promise.allSettled vs Promise.race in JavaScript: Differences and When to Use Each (Tested Examples)](https://mfaysaldev.hashnode.dev/javascript-promise-all-vs-allsettled-vs-race?utm_source=hashnode&utm_medium=feed)

Promise.all waits for every promise to fulfill and fails fast on the first rejection. Promise.allSettled waits for every promise to finish and always fulfills with an array of {status, value|reason} r

12 min read · [mfaysaldev.hashnode.dev](https://mfaysaldev.hashnode.dev/javascript-promise-all-vs-allsettled-vs-race?utm_source=hashnode&utm_medium=feed)
