Tag

#node-js

314 posts73 followers

Explore Hashnode

Alternatives

RONI DAS5h ago · 9 min read

Do Not Trust process.versions.brotli. How to Check Node.js, .NET and Envoy for the Brotli Bug (CVE-2026-111497)

Do not use process.versions.brotli to decide if your Node.js is safe from the new Brotli bug. I ran it on the official, patched Node.js 24.22.1 build from nodejs.org on 31 October 2026. It printed 1.2

systemdesignacademy.hashnode.dev

Cruxtab Technologies Pvt. Ltd.23h ago · 3 min read

How to Test Merchant-Configured Integrations in a Shopify Form Builder

Connecting a form to an external service is only the beginning. Before merchants rely on that connection, developers need to verify that configuration, submission processing, API requests, and error h

cruxtab-technologies.hashnode.dev

Cruxtab Technologies Pvt. Ltd.1d ago · 3 min read

Centralizing Application Error Reporting with Slack

When an application encounters an unexpected error, the first challenge is often discovering that something went wrong. Without centralized reporting, developers may need to reproduce the issue locall

cruxtab-technologies.hashnode.dev

Cruxtab Technologies Pvt. Ltd.2d ago · 4 min read

Cleaning Up Amazon S3 Files During Shopify App Uninstall

Many Shopify apps allow merchants or customers to upload images, documents, signatures, and other files. These uploads often live in object storage rather than the application's primary database. When

cruxtab-technologies.hashnode.dev

Cruxtab Technologies Pvt. Ltd.3d ago · 4 min read

Coordinating Database and S3 Cleanup When Deleting Form Submissions

A form submission may contain more than text fields. It can also be associated with uploaded files stored in object storage. When a merchant deletes a submission, removing only the database record may

cruxtab-technologies.hashnode.dev

Steven Anongo4d ago · 3 min read

Understanding Threads in Node.js

One concept that confuses developers who are new to Node.js is how it can be single-threaded and non-blocking, support asynchronous operations, and still use multiple threads for certain tasks. To und

amstevee.hashnode.dev

Sulakshana KarunarathneOct 15 · 5 min read

Hardening a 3-tier app before Kubernetes: 6 things that were quietly broken

Kubernetes gives you strong security controls: runAsNonRoot, read-only root filesystems, readiness-based routing. But they only work if your containers already support them. So before moving Deal Aggr

devseccloud.hashnode.dev

Aditya Kumar GuptaOct 15 · 23 min read

BullMQ with Node.js and Redis

Imagine you're building an e-commerce application. Whenever a customer places an order, your application needs to: Save the order in the database. Send an order confirmation email. Generate an invo

blog.adityaguptareal.com

Harrison GuoOct 12 · 14 min read

Observability and Billing for AI API Calls: A T-Shaped Architecture

Adding AI API calls to an existing backend is where most teams' observability and billing instincts break. The calls look similar to any other RPC — send a JSON request, receive a JSON response. The d

harrisonsec.hashnode.dev

Harrison GuoOct 8 · 8 min read

Use-After-Free Is a Lifetime Bug, Not a C Bug

Use-after-free gets taught as a C problem. The lesson lands as "C lets you touch freed memory, so C is dangerous, so use a safer language." That is true and it is also the wrong lesson, because it hid

harrisonsec.hashnode.dev

Search Hashnode

Explore Hashnode

Trending tags this week

Do Not Trust process.versions.brotli. How to Check Node.js, .NET and Envoy for the Brotli Bug (CVE-2026-111497)

How to Test Merchant-Configured Integrations in a Shopify Form Builder

Centralizing Application Error Reporting with Slack

Cleaning Up Amazon S3 Files During Shopify App Uninstall

Coordinating Database and S3 Cleanup When Deleting Form Submissions

Understanding Threads in Node.js

Hardening a 3-tier app before Kubernetes: 6 things that were quietly broken

BullMQ with Node.js and Redis

Observability and Billing for AI API Calls: A T-Shaped Architecture

Use-After-Free Is a Lifetime Bug, Not a C Bug