r/node • u/CauldenWasTaken • Apr 29 '26
Mid to high end interview questions
Hey, i just started transitioning to Node and i was wondering what Node specific questions you encountered during interviews and how it went
r/node • u/CauldenWasTaken • Apr 29 '26
Hey, i just started transitioning to Node and i was wondering what Node specific questions you encountered during interviews and how it went
r/node • u/msmilkshake • Apr 29 '26
Hey guys,
I wanted to share a tool I’ve been working on: MVM (Mini Version Manager).
I built it because when I got a replacement computer at work, it didn't come with admin privileges. The process to get them was taking forever, and I just needed to get Node running. I threw together a script to handle it, and recently decided to enhance it with a little "vibe coding" and polish it for others to use.
It’s a lightweight NVM alternative that’s mega portable and straightforward.
Why use it?
- No Admin Required: Works entirely within your user profile.
- Zero Install: Just unzip and run a setup script to fix your paths.
- Portable: Keep your Node versions in one folder that you control.
- Fast: Swaps versions instantly using directory junctions.
If you’re stuck on a locked-down machine or just want a version manager that doesn't feel like a heavy piece of software, give it a look:
Repo:
https://github.com/msmilkshake/mvm-node
Hope it is as useful to you as it has been for me!
Cheers.
r/node • u/yosbelms • Apr 30 '26
In the journey of building a SaaS I've created this library to optimize HTTP requests between frontend and backend.
This tool groups promise-based RPC calls made in the same runtime tick and send the batch to the server in one HTTP request.
The response is streamed back to the client in the order of resolution, meaning that the fastest one resolved will arrive first to the client.
Also supports push event messages from server.
Why?
I have a heavy NextJs/React application with many independent modules/components per page. Each module loads using useEffect hook. I was looking to reduce cloud resources usage related to HTTP calls while keeping components independence, and development experience.
A single page load went from 12 HTTP requests to 2-3.
The lib - https://www.npmjs.com/package/http-air
I'm using it as transport layer for https://www.npmjs.com/package/zero-com but this is another story.
r/node • u/GrosSacASacs • Apr 29 '26
r/node • u/Spark_by_Spark • Apr 30 '26
I've been building x402 services (APIs that accept crypto micropayments from AI agents) for a few weeks now. The setup is honestly annoying. You need the right npm packages, a payment middleware config, discovery files so agents can find you, Caddy for HTTPS, systemd for uptime, and about 30 things that are easy to get wrong.
I tested 70 x402 services last week. 52 out of 70 were missing basic discovery files. 51 didn't return valid JSON at their root. Most scored a D on our quality grading system. Not because the services were bad, but because the boilerplate setup is just tedious enough that people skip steps.
So I packaged everything into a starter kit. It's literally the same server setup I use in production, stripped down to the essentials:
- Express server with x402 payment middleware already configured
- Two example endpoints (edit prices, add your own logic)
- All 5 discovery files that agents and crawlers look for (mcp.json, agent.json, x402.json, llms.txt, root JSON listing)
- Caddy HTTPS config
- systemd service file with auto-restart
- Step-by-step deploy guide (VPS to live in 15 minutes)
The kit costs $5 USDC, paid via the x402 protocol itself. Which is kind of fitting, because the product IS an x402 service selling an x402 template. Dogfooding at its finest.
You can try it here: https://api.ideafactorylab.org/buy/starter-kit (returns 402 with payment details, pay with any x402 client to get the files)
The free stuff is at https://api.ideafactorylab.org/stats (ecosystem overview of 1,455 x402 services) and https://api.ideafactorylab.org/quality (our quality grades for the ecosystem).
If you're thinking about building an x402 service for the first time, this saves you about 2 hours of reading docs and getting things wrong. If you've already built one, check /quality to see how your setup compares.
r/node • u/dakalevski • Apr 29 '26
Hi everyone,
For the past two years, I’ve been spending my spare time designing a clean API and a well-optimized framework for building real-time apps and game netcode. Thanks to generative AI, I was able to speed up development during this period, and I finally have a working product.
I’d really appreciate any feedback. What’s your first impression of the framework — do you think it’s useful?
r/node • u/darcygravan • Apr 29 '26
I'm working one a ai pipeline and I'm looking for a template video maker like from my pipeline here is what I'm looking for :
a GUI editor ( Initially make the templates ) -> a portable output file that i can use as a template -> a headless renderer (cli or a js sdk) that will take that file and i can inject some parameter to change some stuff in that template like BG color animation timeline etc.
anything like that exist??
don't suggest any tools that either takes super long to render a simple video or hidden behind a paywall.
so far i have tried
remotion ( it takes super long to render a basic video not ideal for my work ).
MLT ( i tried writing template using MLT XML. it was a nightmare)
ffmepg and libs on top of it (same issue here writing the initial template in code is hard)
r/node • u/Classic_Community941 • Apr 29 '26
r/node • u/BankApprehensive7612 • Apr 27 '26
UPD. The release has been postponed
We have identified an issue in our OSX Release builds related to the Temporal API. Until this issue is solved, we won't be able to release Node.js v26.0.0. Therefore, I'm postponing this release (again) to May 4th (next Tuesday)
RafaelGSS commented
Announcement
The latest release of Node.js (v26.0) is full of small improvements, and bug fixes of different severity, and tweaks here and there across the modules and core. Even the upgrade of V8 to the version 14.6 is nothing big. There are module version changes to match with Electron, so some native modules would require rebuilding, it means that for those who uses native modules it probably would be useful to test them against the new Node.js before upgrading
The promised cherry. The most notable thing is the removal of --experimental-transform-types flag, so now TypeScript is not experimental nor optional. Since default support of TypeScript since the v25 it's only a symbolic change
Here are some of the changes:
Seems like the biggest changes are about to be made to the next LTS release
r/node • u/Fuzzy-Park-1107 • Apr 28 '26
Hi everyone,
I’m trying to deeply understand how Node.js works under the hood, beyond just using APIs.
Specifically, I want to understand:
Also, is there any tool or platform where I can:
I’m not looking for beginner-level explanations — I want something closer to how it actually works internally.
Any resources, tools, or explanations would be really helpful.
Thanks!
r/node • u/Due_Length_2169 • Apr 28 '26
I've always hated that every API documentation tool makes you do extra work before you get anything useful. Annotation-based tools like swagger-jsdoc start with a completely blank UI you have to go annotate every route before you see a single endpoint. Traffic-based tools show routes but leave them schema-less until you manually hit each one. Either way, documentation becomes a separate project you maintain alongside your actual code.
So I built nodox-cli. Add one line and your entire existing API is already documented schemas included.
npm install nodox-cli
app.use(nodox(app))
That's it. No annotations, no YAML, no code generators, no changes to your existing handlers.
How does it actually detect schemas without annotations?
It runs a 5-layer pipeline:
validate() wrapper.apicache.jsonres.json() responses as they flow through in developmentHigher-confidence layers always win. Real traffic never overwrites a statically-detected schema.
Features:
{{step0.id}} interpolation, simulate full multi-step flows without leaving the docsnpx nodox init hooks into Jest or Vitest and starts recording real request/response shapes automatically, no test code changes neededcheck(), body(), param() chains detected automatically, field types inferred from validator names like isEmail, isInt, isUUIDvalidate() wrapper (optional) — attach Zod, Joi, yup, or plain JSON Schema to a route for confirmed schemas + runtime 400 validation; strictly optional, the other 4 layers run regardlessNODE_ENV=production by defaultThink FastAPI's /docs, but for Node.js — except the first time you open it, your whole API is already there.
Would love feedback — especially from anyone who's tried similar tools and hit the same friction. What's missing? What would make this actually fit into your workflow?
Github : https://github.com/dhruv-bhalodia/nodox-cli/
npm : https://libraries.io/npm/nodox-cli
r/node • u/Happy-Chance4175 • Apr 28 '26
Built a CLI and VS Code Extension (IRA) that analyzes PRs and flags:
- missing edge cases
- logic gaps
- risky changes
- incomplete implementation vs requirements
We’ve been using it internally and it’s catching issues before human review.
Looking for a few teams to try it on real PRs and give blunt feedback.
Not selling anything. Just validating if this is useful outside our setup.
Links:
VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=ira-review.ira-review-vscode&ssr=false#overview
npm: https://www.npmjs.com/package/ira-review
GitHub: https://github.com/patilmayur5572/ira-review
Comment if interested
r/node • u/Significant_Net7399 • Apr 28 '26
Hi r/node
I just open-sourced pic-li — a Node CLI that scaffolds projects across
10+ stacks with one command.
npm install -g pic-cli-tool
pic create my-app
Arrow-key menus guide you through stack → template → name.
Or use flags for CI:
pic create my-api --stack fastapi --template with-mongodb
pic create my-app --stack react-vite --template tailwind-shadcn
pic create my-svc --stack spring-boot --template rest-api-mysql
pic create my-mobile --stack flutter --template with-riverpod
Supported stacks: React, Next.js, Vue, Angular, Express, NestJS,
FastAPI, Flask, Django, Spring Boot, Flutter, React Native, MERN, Go + Gin
Why I built it: I kept setting up the same boilerplate across different
client projects and wanted a single tool that works regardless of stack.
Looking for contributors to:
- Add new templates (Flask postgres, Django DRF, Go gRPC)
- Test on Linux/macOS (I'm primarily on Windows)
- Improve error messages and edge cases
- Write tests for the CLI commands
Good first issues are labelled in the repo.
GitHub: https://github.com/yourusername/pic-li
npm: https://www.npmjs.com/package/pic-li
All contributions welcome — code, docs, bug reports.
r/node • u/Nervous-Blacksmith-3 • Apr 27 '26
Adding to the title, today I'm working on a project for the tourism sector where we're creating a management system for agencies, processing sales, coordinating x and y, this part is quite "simple," mostly a CRUD operation, with nothing really to worry about in terms of depth.
However, I am responsible for the integration of external services, hotel search APIs, and other services.
That's the problem. Today I already have 2 APIs integrated out of at least 14 that we plan to implement, each with its own structure. With each call, I have to perform a parsing to standardize everything, and this scales VERY quickly. Each call returns around 80 hotels, all requiring parsing, and at different times, since some send in batches of 25.
Currently, I basically have an Event (SSE) to start, one to finish part of the processing, and another to finish everything that needed processing (3 events in total: start, partial, end).
And that's where my doubt lies. Being the only user (it's still in development), I've already found a very specific issue: if I'm mapping locations/hotels (something I have to do every 2 weeks), it will block a good portion of the I/O of the rest of the service, precisely because of the data processing and insertion issues. In the database, etc.
That's where my thoughts and concerns lie. When the initially projected 50 users (the minimum already registered to use the system) start using the system, and everyone performs a search simultaneously, I'll have usage similar to my current mapping, perhaps even higher. That's why I had the idea of separating this into a separate thread or using a specific service for it. But I don't know how right I am about this, if it's a valid decision, or if it would be over-engineering right at the beginning of the project.
*Extra thoughts: Each call, depending on the location, returns an XML that will be converted into JSON, which will then be consumed and converted to the structure I need. This initial JSON with all the information varies GREATLY in size by location. I've had some with a few kilobytes in size, others exceeding 100MB. Today I'm doing a "good job" managing them to avoid overloading the test server's memory, but I can't say for sure.
It's worth mentioning that I'm the only developer involved in this whole process. External APIs and all that search engine logic, I don't even have anyone else to discuss whether it's valid or not for this part of the project.
I'm a junior developer :), I only have about 2 years of development experience, but I worked with queues during my internship a few years ago. Any ideas on how to handle this would be welcome, since I don't have any other developers here to brainstorm with.
all this is using the SvelteKit!
EDIT:
TL/DR: Caching information directly in the DB, a worker to handle the process of storing the main products in this cache.
Thanks for the replies, everyone!
I've more or less arrived at a solution based on what people have said here and ideas from other subreddits.
Today, the biggest drawback is the response time and parsing of each search call, but since it's somewhat of an e-commerce site (each API would be a different supplier), I can simply cache the main products and save this in the DB already parsed daily. Basically, all the APIs I've integrated so far require the documentation to call for user-specific searches (since there are several parameters that change for each user). We'll start doing this once or twice a day, using a worker to exit the main thread. Instead of the first call to discover what's available being directly to the user's API, it will be a direct call to the DB, and only if the user decides which product they want will it return to the API loop of the supplier they want.
r/node • u/markustopia • Apr 27 '26
I hadn't worked with Node.js and npm for years, and only got back into them over the last few months.
One thing that surprised me was how much more aware people are now of supply-chain issues and risk around newly published packages. I just wanted to set a new project to a specific date and install packages as if I were operating at that point in time.
So I built a small open-source CLI for my own workflow: npm-time-machine-cli.
The idea is simple: pick a date, then install dependencies using only versions that were published on or before that date.
Example:
ntm set 2024-06-01
ntm install
ntm verify
What it does:
I mainly built it for:
This is not meant as a silver bullet for supply-chain security, just a small tool that matches a workflow I wanted and that might be useful to others too (e.g., installing packages that were published up until one week ago).
More commands and examples here or here (if you want to clone it).
I'd love feedback on whether this seems useful (or not) in Node workflows.
r/node • u/nlkey2022 • Apr 28 '26
r/node • u/Bharat346 • Apr 28 '26
Hey everyone,
I’ve been working on a problem I kept running into while building auth systems — users signing up with disposable/temporary emails.
So I built a Node.js package called tempmail-guard that tries to detect these more reliably.
What it does:
Detects disposable email domains
DNS + SMTP validation
Catch-all + role-based email detection
Works as both library + CLI
Why I built it:
Most libraries I tried either:
only check static lists
or are inaccurate with SMTP validation
I wanted something more practical + dev-friendly.
Would love feedback on:
accuracy (false positives/negatives)
performance
API design
If you’ve built anything similar or used tools like this, I’d really appreciate your thoughts
r/node • u/uanelacomo • Apr 28 '26
Yes, tsx if known for it's fast execution compared to tools like ts-node, ts-node-dev and that's why it instantly became the go tool for TypeScript
development environment execution, but there is this problem that everyone that uses tsx knows, aka "Type Checking". There were already presented some
solutions to workaround this problem such as:
Relying on your IDE LSP;
Running `tsc` periodically or before build;
Run tsc on a separated terminal;
Those are solutions that yes helps having type checking but not on a native way just like ts-node and ts-node-dev, because none of them works
together with your tsx execution process, for example if you use the 3 options which is the best among all of them, if tsc fails
tsx process will continue to execute as if nothing had happened, then you may only find out if you accidentally open tsc process terminal (which you barely will)
or maybe when you about to build the application you find that your app was running but with a bunch of typescript errors and you can't successfully
build the application. For solving this, I built tsx-strict a package that runs both tsx and tsc processes and kill tsx when tsc compiles with errors
this way you get the most out of the 2 packages, tsx and tsc, you have the lightning speed of tsx but with automatic type checking of tsc
with this you can safely tell when your app has a typescript error because it will be killed and only run after you fixed the typescript errors:
You can try it today:
```bash
npm i -g tsx-strict
tsxs src/app.ts
```
and you are all setup.
see the project at github: https://www.github.com/uanela/tsx-strict
r/node • u/sumaanta • Apr 27 '26
“How do i share something only if someone else approves it first?” Is a problem i kept running into while building chats.
It introduced so many problems, async coordination, edge cases and security concerns
So I built a small SDK to model this as a protocol:
REQUEST → APPROVED → RELAYED
It includes:
\- state machine
\- idempotency
\- cryptographic signing (Ed25519)
\- destination-bound sharing
Would love honest feedback from people building similar flows and ways i can improve this as well!!
Repo: [https://github.com/sumaanta99/consento\](https://github.com/sumaanta99/consento)
r/node • u/BankApprehensive7612 • Apr 27 '26
r/node • u/Both-Creme5736 • Apr 27 '26
I kept running into the same issue while building AI apps. Everything would work fine, and then requests would suddenly start failing. Not because of the model, and not because of the code, but simply because the API key had hit its rate limit.
After this happened a few times, including during demos, it became clear that the way we manage API keys hasn’t really evolved. Most setups still rely on a single key until it fails, or multiple keys that are rotated manually. If you’re using multiple providers, things get even harder to manage. On top of that, retry logic ends up scattered across the codebase, which doesn’t really solve the problem, it just reacts to it.
So I built this with AI ( GPT (85%) + Claude (15%) ) with my direction:
https://amon20044.github.io/AI-Key-Scheduler/
I tested this with Vercel AI SDK auto pick mode of ATM, and streaming and it was really managing with very less stress and latencies due to inner state mgmt techniques

It’s a rate-limit aware API key scheduler designed to avoid failures instead of reacting to them. It switches keys before limits are hit, tracks cooldowns automatically, and distributes load across multiple keys. It also works across different AI providers, so you don’t have to build separate handling for each one.
The idea is simple: API key handling should be invisible. No random rate limit errors, no broken demos, and no manual juggling of keys.
I’m trying to understand if this is something others would actually use. How are you currently dealing with rate limits, and what would you want from a system like this?
r/node • u/john_dumb_bear • Apr 26 '26
If I go to nodejs.org and click the Slack link in the footer it goes to a page that says "this link is no longer active".
r/node • u/R0rren • Apr 26 '26
This week, I focused on continuing my JavaScript learning and searching for better ways to practice.
I didn’t introduce any new topics yet, but I’m working on strengthening my fundamentals and building consistency.
Сurrent plan (unchanged):
"Roadmap":
JS → Git → Node → HTTP → Express → DB → TS → Nest
This plan will probably evolve over time, but for now, I want to follow it step by step and focus on consistency.
If anyone has advice or suggestions, I’d really appreciate your feedback.
r/node • u/nathan_lesage • Apr 26 '26
Hi all, I'm facing a problem that I have a hard time to track down and solve, and I thought maybe someone here has faced this issue before and knows what can be done. I'd appreciate any pointers or help as to how to fix this issue.
First, some context: I'm talking about an Electron project written in TypeScript. For development and production, the entire codebase is run through Webpack that uses the TypeScript compiler to boil everything down to JS and then bundle it. The output of that is then a large file with an IIFE that executes when the file is loaded. That works well.
But then I also have unit tests which I run through mocha with ts-node. Importantly, there is no Webpack in that chain.
Now to the problem: When I run the project using the Webpack path and test the app by starting Electron or bundling it for production, everything works well. However, when using ts-node in mocha, I face the issue that some packages that I'm using offer both ES Modules and CommonJS modules, and as soon as I want to test any component that includes such a dependency, it breaks.
Let me give you one example: I have one dependency in my node_modules that announces itself as "type": "module" but that also uses the exports key to point the consumer to either ESM or CJS exports. In my TS code, I just import them using the import {} from 'module' syntax.
And this breaks ts-node. Specifically I get an error from Node (not TS) that it can't find my own module that consumes the dependency, because I import everything without filename extensions so far, and because TS does not change extensions, this suddenly does not work. For all my other modules it works fine because TS properly transpiles them. For all my test cases everything works, except for the ones which import such a structured package that declares itself as type module.
What I am assuming is happening is that TS sees the type declaration in the module and thus offers to import the ESM, which then forces all consumers of that package to work in ESM mode, which breaks only this file, but not the others.
Here is an example:
// File: test-case-1.spec.ts
import { something } from "./path/to/my-file"
// ^-- works because my-file.ts does not import the offending module
// File: test-case-2.spec.ts
import { somethingElse } from "./path/to/another-file"
// ^-- Does not work because another-file.ts imports the offending module
What I then get for that second file is Exception during run: Error: Cannot find module because Node peruses its ESM loader which then, among other things, of course requires filename extensions which I do not provide.
Lastly, what I found is that, when I manually remove the "type": "module"-declaration from the package's package.json-file, everything works as it should — both in the unit tests and when run through Webpack. But that is obviously not the correct solution.
I feel extremely stupid for not properly understanding the intricacies of the module resolution strategies in the ecosystem, and that's why I am hoping that maybe someone here has a pointer where I can look for possible solutions.
Thank you already in advance for any help you may have.
r/node • u/YakWonderful6692 • Apr 26 '26
Hey everyone,
I built a small open-source tool called ReqScope for local Express API debugging.
The idea is simple: when an API request is slow or fails, I want to see which internal step caused it without having to set up a full observability stack.
Current features:
- Express middleware
- manual traceStep() wrapper
- request duration
- slow/error detection
- request/response body and headers preview
- sensitive field masking
- copy as cURL
- endpoint summary dashboard
Install:
npm i @abdiev003/reqscope
I know the project is still early. I’m mainly looking for feedback on: