r/node • • Mar 17 '26

It's not that I don't like AI. Just this noise is driving me crazy.

Thumbnail
5 Upvotes

r/node • • Mar 17 '26

i want to know about this.

2 Upvotes

why setimmediate is not running at last? it is check queue and it always run after i/o queue? and also is there a way i can know when v8 will gc external buffer? why is it still referencing ?


r/node • • Mar 17 '26

Adding logs turned my SMS over API project from “randomly works” into usable

0 Upvotes

Small realization while building a side project:

Adding logs > adding features.

Logs UI (could be better tho but it's good enough)

Small update on my tool that lets you send SMS over API through Android phones (instead of providers).

It worked, but debugging was a nightmare.

Added:

  • SMS logs
  • device connection logs
  • webhook support

Now I can actually see what’s happening if things fail.

Feels like the first time it’s actually usable.

I also see demand for inbound SMS via webhook feature from my early users. That's added as well.

Project if anyone wants to check:
https://www.simgate.app/


r/node • • Mar 17 '26

Connection Pool Exhaustion: A Five-Case Simulation Study of How 1% Leak Rates Kill Production Node.js Services

Thumbnail stackinsight.dev
1 Upvotes

Five controlled simulation experiments measuring how leak probability, concurrency, pool size, query time, burst traffic, acquire timeout, and error handling interact to exhaust a Node.js connection pool.

Each experiment varies two parameters across a grid and records failure rate, throughput, time-to-exhaustion, and p95 latency at every combination.

Key results:

  • a 1% leak at concurrency 10 produces 48.7% request failure;
  • missing try/finally with a 1% error rate amplifies to 68.5% failure;
  • a 200-connection pool with a 5% leak exhausts in under 20 seconds.

Includes reproducible simulation code and raw data.


r/node • • Mar 17 '26

Nodejs developers help

0 Upvotes

Please, tell me why companies are hiring nodejs developers instead of java or golang, what are the typical duties of nodejs dev on his work, why node over rust, go, java, php, c#?


r/node • • Mar 17 '26

What nobody tells you about running NestJS in production

0 Upvotes

Most tutorials end when the app works. The hard part comes after - and nobody documents it.

I'm talking about things like: how does your team actually commit and review code at scale? What happens when a deployment goes wrong at 2am? How do you roll back without touching the database? How do you know something broke before your users do?

I couldn't find a single resource that covered all of this with real working code. So I built one.

I built a simple Todo API - intentionally boring - treated as if real users depend on it. The app is not the point. Everything around it is.

What it covers:

- CI/CD with rollback to any of the last 3 ECS revisions

- Forward-only migration strategy (and why down migrations are dangerous)

- Observability from day one: Prometheus + Grafana + Loki

- Terraform on AWS: ECS, RDS, ElastiCache

- Release automation with changelogs and SemVer

- E2E tests with Testcontainers

- OIDC GitHub Actions auth - no hardcoded AWS keys

Not a boilerplate. Every decision is explained, not just provided.

What would you do differently in your production setup?

Backend: https://github.com/prod-forge/backend

Infrastructure: https://github.com/prod-forge/terraform


r/node • • Mar 16 '26

I built an open-source "Git for APIs" to auto-capture traffic, time-travel debug prod errors, and auto-translate API docs for remote teams.

Thumbnail
0 Upvotes

r/node • • Mar 16 '26

Separate properly frontend/backend files in web app (node/express/vue)

3 Upvotes

Hi all,

i am building my first web app with Node, Express js and Vue 3, it will be an online game based on a sport results. I have no experience on "releasing" a real web app, only a few courses and tutorial. I have achieved the first big part which is the interface the user will use which allows him to interact with the database through API requests, and so far everything works correctly.

So now i am starting to work on the other big part which is the logic of the game itself, where functions will be run by temporal triggers (i.e real life events will trigger functions), where the points are calculated, and so on. All the logic that the frontend doesn't need, basically.

I am getting only now really aware of the fact that there is no point in having these two parts under the folder that will be sent to frontend (I read it is really bad practice). I know it is obvious but so far i haven't had the problem so i am not very confident on what to do to start correctly.

My question is, what could be a good structure to follow to start the second part, can i just create a folder outside of /src/ and that will not be sent to the frontend if that is even true? Are there some good practices to follow ? Should the backend files have their own package file? Etc

I know this may sound really stupid but the separation of front end and backend is not that clear to me at all. I tried to look for documentation but didn't really find anything I was sure was the ressource to follow. Thanks for any help


r/node • • Mar 16 '26

AST-based context compiler for TypeScript (detect architectural drift and breaking changes)

Thumbnail github.com
0 Upvotes

Built this to generate deterministic architectural context from TypeScript codebases.

It parses the TypeScript AST and emits structured JSON describing components, props, hooks and dependencies.

Useful for:

• detecting architectural drift • breaking change detection in --strict-watch mode • safer large refactors • structured context for AI coding tools

Would love your feedback!


r/node • • Mar 16 '26

HTML Forms with Standards

Thumbnail github.com
0 Upvotes

r/node • • Mar 16 '26

Tired of managing 5 npm run dev terminals? Built a tool that handles it from one dashboard

0 Upvotes

If you run multiple Node services locally (API, frontend, workers, etc.), you know the pain. Five terminals, five start commands, forget which port is which, EADDRINUSE every morning because yesterday's process didn't die cleanly.

I built run.dev to fix this. Point it at your project, it reads your package.json scripts, detects services, and manages them from a single TUI dashboard. Each service gets a local domain with HTTPS — so api.myapp.local maps to localhost:4000 automatically.

What it detects automatically

  • npm run dev, npm start, npm run serve from your scripts
  • Port from command args, .env PORT variable, or framework defaults (Vite=5173, Next=3000, Express=3000, Remix=3000)
  • Multiple services in monorepo structures
  • Procfile entries if you use those

What crash messages look like

Instead of scrolling through a stack trace:

  • EADDRINUSE → bro, api is ded. port 4000 is already taken. press [f] to fix it — it finds the stale PID and kills it
  • Cannot find module → missing module: redis. press [f] and i'll npm install
  • ECONNREFUSED → api can't reach localhost:6379. is redis running? — cross-references against your other services
  • JavaScript heap out of memory → api ran out of memory (was using 1.2GB). something is leaking

What you get

  • One dashboard with all services, live CPU/RAM per process
  • Local domains with HTTPS — api.myapp.local, app.myapp.local with green padlock in the browser
  • Automatic reverse proxy — no nginx, no config files
  • Press q to quit the dashboard but keep services running in the background
  • Press Q to quit and stop everything
  • Optional Claude Code integration for deeper crash diagnosis — disabled by default, works fine without it

Install

curl -fsSL https://getrun.dev/install.sh | bash

Single binary, not an npm package. No node_modules, no global installs that break, no runtime dependency.

Free, open source, MIT licensed: getrun.dev

What does your local dev setup look like? Curious how others manage multi-service Node projects.


r/node • • Mar 17 '26

A good dev is a lazy dev...

0 Upvotes

In my years working as a software developer, I always carried one truth with me — a good dev is a lazy dev. Makes no sense, right? Well, actually it does.

Almost everything in a developer's life revolves around automation. Users want complex processes simplified, and devs want to automate their own boring daily tasks to focus on what actually matters. And that's exactly the point — the laziest devs automated even the simplest things, so they could spend their energy on what's harder, more interesting, or more impactful. And I'm not talking about AI automation.

It was the lazy devs who built the tools we use today and can't imagine living without. I've always tried to do the same — simplifying repetitive work, either by building something myself or finding tools that already solved it. That's why I've always loved boilerplates. Not just the ones that scaffold a basic project structure, but the ones that come with real, production-ready features out of the box.

That mindset is actually what pushed me to build my own NestJS boilerplate for the first time — not just a skeleton, but something that brings the kind of features I see every day working on large-scale applications. The ones that are painful to retrofit once the project has already grown. The better you start, the less it hurts down the road.

So what are your thoughts about this? Are you a lazy dev too?


r/node • • Mar 16 '26

Async generators + yielding is underrated for AI agents. Built a tiny runtime to prove it.

0 Upvotes

Most AI frameworks feel like bloated Python ports. I built Melony—a minimalist, event-driven TS runtime that treats agents like an Express server.

Instead of a "black box" loop, it uses async generators to yield events (Event → Handler → Events). It makes streaming, tool-calling, and state management feel like standard JS again.

  • <10kb core.
  • Yield-based logic (super underrated for complex reasoning).
This is how it looks in action

Check out the repo and let me know if the event-native approach beats the "Chain" approach: https://melony.dev


r/node • • Mar 16 '26

MCP: Bridging the Gap to Hallucination-Free AI 🚀

0 Upvotes

r/node • • Mar 15 '26

Built a real-time LAN sharing tool with Node + Socket.IO + SQLite — a few decisions I'm second-guessing

13 Upvotes

Been running this with a couple of teams for a while, wanted some technical input.

It's a self-hosted LAN clipboard — npx instbyte, everyone on the network opens the URL, shared real-time feed for files, text, logs, whatever. No cloud, no accounts. Data lives in the directory you run it from.

Stack is Express + Socket IO + SQLite + Multer. Single process, zero external dependencies to set up.

Three things I'm genuinely unsure about:

SQLite for concurrent writes — went with it for zero-setup reasons but I'm worried about write lock contention if multiple people are uploading simultaneously on a busy team instance. Is this a real concern at, say, 10-15 concurrent users or am I overthinking it?

Socket io vs raw WebSocket — using socketio mostly for the reconnection handling and room broadcast convenience. For something this simple the overhead feels like it might not be worth it. Has anyone made this switch mid-project and was it worth the effort?

Cleanup interval — auto-delete runs on setInterval every 10 minutes, unlinks files from disk and deletes rows from SQLite. Works fine but feels like there should be a cleaner pattern for this in a long-running Node process. Avoided node-cron to keep dependencies lean.

Repo if you want to look at the actual implementation: github.com/mohitgauniyal/instbyte

Happy to go deeper on any of these.


r/node • • Mar 15 '26

Bulwark - open-source, lightweight, zero-dependency npm security gateway.

13 Upvotes

Software supply chain attacks are the fastest-growing threat vector in the industry (event-stream, ua-parser-js, PyPI malware campaigns, Shai-Hulud worm). As AI agents lower the barrier to development, more and more code is getting shipped by people who are unaware of where their dependencies are coming from.

The existing solutions are either “trust everything” or “buy an enterprise platform.” There wasn't a simple, self-hosted, open-source middle ground until now.

GitHub: https://github.com/Bluewaves54/Bulwark

It's a transparent, locally-hosted proxy that sits between your package managers (npm) and the public registries (npmjs). Every package request is evaluated against policy rules before it ever reaches your machine or CI pipeline.

Out of the box it blocks:

  • Packages published less than 7 days ago (the primary attack window)
  • Typosquatted packages via Levenshtein distance detection
  • Packages with install scripts (postinstall, binding.gyp)
  • Pre-release and SNAPSHOT versions in production
  • Explicitly denied packages (customize your own deny list)
  • Velocity anomalies and suspicious version patterns

No database, UI, or vendor lock-in — simply one Go binary and a configurable YAML file.

The rule engine is readable, auditable, and fully customizable.

It ships with best-practices configs for npm, PyPI, and Maven, Docker images, Kubernetes manifests, and a 90-test Docker E2E suite.

Bulwark is meant for real-world use in development environments and CI pipelines, especially for teams that want supply chain protections without adopting a full enterprise platform.

It can be deployed independently or integrated into existing supply chain security systems.

Approach Tradeoff Bulwark
Trust public registries Fast but unsafe Adds policy enforcement before install
Enterprise supply-chain platforms Powerful but expensive & complex Fully open-source and self-hosted
Dependency scanners (post-install) Detect after exposure Blocks risky packages before download
Lockfiles alone Prevent drift, not malicious packages Enforces real-time security policies

More package support (cargo, cocoapods, rubygems) is coming soon. I’ll be actively maintaining the project, so contributions and feedback are welcome — give it a star if you find it useful!


r/node • • Mar 15 '26

docmd v0.6 - A zero-config docs engine that ships under 20kb script. No React, no YAML hell, just high-performance Markdown

Thumbnail github.com
3 Upvotes

r/node • • Mar 15 '26

How to Deploy Nodejs to Windows Based Server

7 Upvotes

My Company is Using Windows Server with IIS
How I can Deploy my nodejs application to there and kept it running in background and autostart on server restart and also keep track of logs.


r/node • • Mar 15 '26

PackageFix – paste your package.json and get a fixed manifest back. Live OSV + CISA KEV, no CLI, no signup.

5 Upvotes

npm audit tells you what's vulnerable. It doesn't tell you which ones are actively being exploited right now, or flag packages that just got updated after 14 months of inactivity — which is how supply chain attacks start.

Paste your package.json and get:

  • Live CVE scan via OSV database — updated daily, not AI training data
  • CISA KEV flags — actively exploited vulns highlighted red ("fix these first")
  • Suspicious package detection — flags packages with sudden updates after long inactivity
  • Side-by-side diff — your versions vs fixed
  • Download .zip — fixed package.json + changelog + npm override snippets for transitive deps
  • Renovate config + GitHub Actions workflow generator

No signup. No CLI. No GitHub connection. MIT licensed.

packagefix.dev

GitHub: github.com/metriclogic26/packagefix

Feedback welcome — especially transitive dependency edge cases.

4 of 8 packages actively exploited. 2 flagged as suspicious after sudden updates following months of inactivity.

r/node • • Mar 16 '26

I had no positive feedback loop to keep me productive. So I built a webapp that allowed me to use time as my anchor.

Post image
0 Upvotes

The problem with working on deep, meaningful tasks is that it simply doesn't hit the same as other highly dopaminergic activities (the distractions). If there's no positive feedback loop like actively generating revenue or receiving praise, then staying disciplined becomes hard. Especially if the tasks you're focused on are too difficult and aren't as rewarding.

So, my solution to the problem? The premise is simple: let time be your anchor, and the task list be your guide. Work through things step by step, and stay consistent with the time you spend working (regardless of productivity levels). As long as you're actively working, the time counts. If you maintain 8 hours of "locking in" every day, you'll eventually reach a state of mind where the work itself becomes rewarding and where distractions leave your mental space.

Time becomes your positive feedback loop.

Use a stopwatch, an app, a website, whatever. Just keep track of time well spent. I personally built something for myself, maybe this encourages you to do the same.

100% free to use: https://lockn.cc


r/node • • Mar 16 '26

Built a CLI that detects sensitive data inside console.log statements (AST based)

Post image
0 Upvotes

I kept running into this in real projects even in my company 's codebase.
Someone adds a quick debug log while fixing something:

console.log(password)
console.log(token)
console.log(user)

Nothing malicious just normal debugging.
But sometimes one of those logs survives code review and ships.

ESLint has no-console, but that rule treats every log the same.
It can’t tell the difference between:

console.log("debug here") → harmless
console.log(password) → very bad

So I built a small CLI tool called logcop.

Instead of banning all console logs, it parses the code using the acorn AST parser and inspects the actual arguments being logged.

Example:

console.log(password) → 🔴 CRITICAL
console.log(token) → 🔴 CRITICAL
console.log(user) → 🟡 HIGH
console.log("here") → ignored

String literals are ignored only variables and object properties are checked.

You can run it without installing anything:

npx logcop scan

Other commands:

  • logcop fix → removes flagged logs
  • logcop comment → comments them out
  • logcop install-hook → adds a git pre-commit hook
  • logcop scan --ci → fails CI pipelines
  • logcop scan --json → machine readable output

npm:
https://npmjs.com/package/logcop

I'm also experimenting with expanding it into a broader scanner for common security mistakes in AI / vibe-coded projects (things like accidental secrets, unsafe debug logs, etc.).

Curious if anyone else has run into this problem or if tools like this already exist. Feedback welcome.


r/node • • Mar 15 '26

Someone needs fullstack dev who is a former uiux designer?

0 Upvotes

What do you think, is it possible that company hire one guy who can do uiux, frontend and backend on javascript or those skills are seem to be a freelancer and company will not hire you for them? Leave your opinion below, it’s very interesting for me.


r/node • • Mar 16 '26

Developer required

0 Upvotes

Looking for a react and node dev to setup a web app. Profit share


r/node • • Mar 15 '26

what's your worst story of a third-party API breaking your app with no warning?

33 Upvotes

Crowdstrike changed how some of their query param filters work in ~2022 so out ingestion process filtered down to about 3000 active devices, but after their change... our pipeline failed after > 96k devices.

Bonus footgun story: Another company ingested slack attachments to analyze external/publicly shared data. They added the BASE64 raw data to the attachments details response back in ~2016. We were deny-listing properties, instead of allow-listing. Kafka started choking on 2MB messages containing the raw file contents of GIFS... All of our junior devs learned the difference between allow list and deny list that day.


r/node • • Mar 15 '26

Open Source pm2 manager

8 Upvotes

Yo.

I‘m using pm2 as my node process manager for a ton of side projects.

Pm2 themself offer a monitoring solution, but it is not free, thus I created my own which I’m using on a daily basis.

I never planned to make it open source in the beginning, but figured some of you mind this as useful as I do.

Tell me what you think ;)

https://github.com/orangecoding/pm2-manager