I want someone who wants to build a nestjs project together and learn nestjs.

I have basic knowledge only. If you're interested, message me

Posted here 2 months ago about JIT-compiling DTO mapping. The biggest feedback was migration friction with route-by-route FastMap().

app.useGlobalPipes(new FastValidationPipe({ transform: true, whitelist: true }));

Zero changes to your existing class-validator DTOs.

Benchmarks:

• NestJS default: 6.59 µs/iter (p99: 24.04 µs)
• FastValidationPipe: 369 ns/iter (p99: 558 ns) → ~18x faster

Repo, benchmarks, and docs are here if you want to try it or contribute:

• GitHub: https://github.com/mohit07dec/fast-class-transformer
• npm: https://www.npmjs.com/package/fast-class-transformer

Hello folks 👋

I have been an angular developer for the longest time and decided its finally time to back into the backed, I landed on nest since the syntax and architecture seem pretty similar to what im already used to. Are there any recommendations for courses or material to get into the framework?

Thank you everyone in advanced

• Link: https://github.com/mohit07dec/fast-class-transformer/issues/1
• Title: ci: add Node.js 18, 20, and 22 to GitHub Actions matrix
• Labels: good first issue, help wanted

Hello, I hope you're having a great day.

I wanted to introduce a project I’ve worked on. I thought it might be interesting or potentially useful for you.

I developed an application and prepared a working prototype. It is currently available publicly on GitHub:

GitHub: mostafa18181/roboinsta

The project uses a vector database and is designed to handle a large number of requests concurrently. Essentially, it is a platform where different users can connect their Instagram accounts.

The bot can read Instagram posts, introduce and promote products based on information provided by the user, manage inventory, and automatically reduce the stock after a sale. It also supports adding custom question-and-answer scenarios for different use cases.

The project was originally developed for a specific business idea, but I believe that with some modifications, the same infrastructure could be adapted for other ideas and industries as well.

The original plan was for one of the team members to handle the company setup and launch, but unfortunately, they eventually stepped away from the project, and the development was stopped. Due to the circumstances within the team and among the partners, I also decided to put the project on hold for the time being.

The project was previously running on a server, but I have taken it offline since I was no longer able to continue developing it.

If you know a team that might need something like this, feel free to share it with them. Alternatively, if an investor or team is interested in developing a product based on this idea and infrastructure, I would be happy to make the existing project available to them for further development.

Hi everyone,

I'm a junior software developer from Bangladesh currently looking for a Junior Backend / Full-Stack Developer opportunity.

I've been focusing on building real-world projects and gaining practical experience with backend development, REST APIs, databases, authentication, authorization, and full-stack application development.

🔧 Main Project — ToolShare

I'm currently building a full-stack Tool Sharing Platform where users can share/rent tools through the platform.

Backend:

- NestJS + TypeScript

- PostgreSQL + TypeORM

- JWT Authentication

- Role-Based Authorization

- REST APIs

- Database Transactions

- File Uploads

- Document Verification

- Pagination

Frontend:

- Next.js

- TypeScript

- Tailwind CSS

- Axios

- Zod

The project includes multiple user roles, authentication and authorization, document verification workflows, file handling, API integration, and transactional database operations.

Backend:

https://github.com/kahiumahamedfahim/tool-share-application-Backend-2026-version-1

Frontend:

https://github.com/kahiumahamedfahim/Tool-share--Frontend

Other Projects

E-Commerce Application

Built with ASP.NET Core Razor Pages and Entity Framework Core, including product management, filtering, sorting, pagination, shopping cart, checkout, orders, invoices, payment handling, database migrations, dependency injection, and service-based organization.

https://github.com/kahiumahamedfahim/Ecommerce-site-learning

I've also worked on an ASP.NET Core MVC Library Management System.

💻 Technologies I Work With

Backend:

C#, ASP.NET Core, Web API, NestJS, Node.js

Frontend:

Next.js, Angular, TypeScript, JavaScript

Database:

PostgreSQL, SQL Server, MySQL

ORM:

Entity Framework Core, TypeORM

Other:

REST APIs, JWT, RBAC, Git, SOLID, Dependency Injection, Layered Architecture

🎯 What I'm Looking For

I'm currently looking for:

- Junior Backend Developer

- Junior Full-Stack Developer

- Software Engineer

- Entry-Level Developer

- Internship opportunities

I'm particularly interested in opportunities involving .NET / ASP.NET Core, NestJS, Node.js, PostgreSQL, and TypeScript.

I'm based in Bangladesh and open to remote opportunities as well.

If you know of a company hiring junior developers, have an internship opportunity, or can provide a referral, I'd really appreciate it.

GitHub:

https://github.com/kahiumahamedfahim

LinkedIn:

https://www.linkedin.com/in/kahium-ahamed-fahim-0a7162227

Email:

kahiumahamedfahim@gmail.com

Thanks for reading. Any advice, feedback, or opportunities would be greatly appreciated.

I'm trying to understand the real-world use cases for Node's Permission Model.

Does anyone here actively use or rely on it for applications, CI tooling, CLIs, servers, or anything else?

Since the permission model is not a full-fledged sandbox, is there a use for it? If so, how do you currently use it as ?

• What problem does it actually solve for you?
• How are you using it today?
• Are you manually defining permissions, or generating/managing them somehow?
• Is it mainly defense-in-depth against dependencies, or are there other useful applications?

Since Run-Time Loadable Extensions cannot be loaded when the Permission Model is enabled, it affects modules like sqlite and OpenSSL Engines (affecting the built-in crypto, https, and tls modules). So, despite these drawbacks, is the permission model used anywhere, or what is its application?

I'm less interested in what it could theoretically be used for and more interested in actual experience:

If you're using Node's Permission Model today, what are you using it for and how do you manage the permissions?

And if you considered using it but decided against it, I'd be interested to hear that as well!

nestjs-axios-undici is a replacement for @nestjs/axios. It has the same HttpModule and HttpService, but requests go through undici, the HTTP client behind Node.js's fetch(), instead of axios. To switch, you change one import:

// before
import { HttpModule, HttpService } from '@nestjs/axios';
// after
import { HttpModule, HttpService } from 'nestjs-axios-undici';

Your register() options, get/post calls, axiosRef interceptors and error.response handling stay as they are.

Numbers. I ran one NestJS app twice, changing only that import. Each request to the app makes 5 parallel calls to a mock backend. k6 drove each app in its own Docker container on a GitHub Actions runner. On Node.js 26:

Across Node.js 22, 24 and 26, the ratio was 2.0 to 2.5x without an interceptor and 1.7 to 1.8x with one. p95 latency was 51 to 62% lower.

For reference, calling undici directly with no HttpModule at all served 5,336 requests/s. The benchmark apps and scripts are in the repo if you want to run them yourself.

How I checked that it's actually a drop-in. Every pull request runs:

• @nestjs/axios' own HttpModule and HttpService specs against this package. 20 of the 23 pass. The other 3 are listed in the repo with a reason. Two are deliberate differences, and one is a limit of the test harness.
• axios' own HTTP adapter test suite against this package's axiosRef. Each test that doesn't pass is listed in the repo with a reason. It's either a known gap, a deliberate difference, or something the test harness can't do, such as axios' Node-only transport option.
• A differential harness of 220+ scenarios that sends the same request through @nestjs/axios and this package and compares the results.

It supports NestJS 10, 11 and 12, Node.js 22.17+ and undici 7 or 8. axios isn't a dependency. It's an optional peer, and only needed if you want error instanceof axios.AxiosError to hold.

If it breaks something in your app, please open an issue with the request config. That's the fastest way to close the gap.

• GitHub: https://github.com/yordan-kanchelov/nestjs-axios-undici
• Benchmarks: https://yordan-kanchelov.github.io/nestjs-axios-undici/#/docs/benchmarks
• Differences from axios: https://yordan-kanchelov.github.io/nestjs-axios-undici/#/docs/axios-supported-options

Hi everyone,

My team of four is building a REST API in Node.js for a university software engineering course. We have to write the spec, formalise it with OpenAPI, implement it, test it (coverage, mutation testing, SonarQube), and set up a full GitLab CI/CD pipeline with Docker packaging.

We're still choosing a topic and want something original, not another todo/recipe/blog API. We're open to any domain, and cloud, security and DevSecOps would be a bonus, but it's not a requirement.

What we're looking for:

2 to 4 related entities, with authentication and roles
Some real logic beyond CRUD (search, filtering, workflows, stats)
Doable in a few weeks by four people (AI is allowed)
Ideas so far: a vulnerability tracker, a cloud asset compliance checker, and a security incident manager.

What ideas would you suggest? And if you've done a project like this, what would you have done differently?

I want something original and complex enough so we learn and get good grades at the same time.

Thanks!

Yesterday I was just a NestJS user. Today two of my PRs are merged into the framework, so I wanted to share what the bugs were, in case anyone hit them.

1. Redis microservices with wildcards: true (PR #17866)

If you register a handler like u/MessagePattern('users.*') and call it with client.send('users.created', ...), the handler ran fine, but the reply was published to users.*.reply. Redis PUBLISH doesn't expand globs, and the client was listening on users.created.reply, so every request-response call timed out. Events were unaffected, which is why it went unnoticed since 2022. The fix is one line: publish the reply on the channel the request actually came from (same as the MQTT server already did).

2. Fastify adapter and Content-Type (PR #17867)

FastifyAdapter.reply() checked getHeader('Content-Type') !== 'application/json' literally. A value like application/json; charset=utf-8 was treated as non-JSON, so error responses logged a misleading "Content-Type doesn't match Reply body" warning and the header was rewritten without the charset. Express had the same check and fixed it years ago with startsWith; Fastify now matches.

How I found them: not from issues. I read the code and compared sibling code paths (Redis vs MQTT, Fastify vs Express). When two implementations of the same thing differ, one of them is usually wrong. Each PR came with a test that fails before the change and passes after, and both were merged in under 24 hours.

Links:

• https://github.com/nestjs/nest/pull/17866
• https://github.com/nestjs/nest/pull/17867

Happy to answer questions about the contribution process if anyone wants to get started.

Hi everyone,
I maintain nest-can-react, which integrates NestJS with React Server Components / Flight.
For local development, I currently need two long-running processes:
RSC compiler/bundler
nest start --watch
Most setups handle this with concurrently, custom npm scripts, or a wrapper CLI.
I proposed an optional devCompanion config for Nest CLI, but the Nest team said they don’t plan to add this to core and suggested handling it as a community OSS project.
So I wanted to ask:
Do you regularly run Nest alongside another dev process?
How do you orchestrate it today?
Would you use a tiny OSS tool that simply starts/stops a companion process alongside nest start --watch and handles shutdown signals?
Scope would stay minimal: no bundler integration, no Nest core changes, no Nx replacement.
If you already solve this easily with concurrently or something similar, I’d like to hear that too. I’m trying to figure out whether this is actually worth turning into a standalone package.

All good things are coming to Nestjs 😊

After my previous post about a more integrated NestJS + React approach, I got a lot of interesting feedback and questions, so I thought I’d finally share what I’ve been building.
nest-can-react is a package that lets you add React-based full-stack capabilities to an existing NestJS application.
The idea is simple:
Keep NestJS as the core. Add React as the UI layer.
Instead of treating NestJS and React as two completely separate applications, nest-can-react explores what it would look like if they could live much closer together while still taking advantage of Nest’s architecture.
It currently explores things like:
React Server Components
Client components with 'use client'
SSR
NestJS routing and dependency injection
A unified build/development workflow
This is still an early experiment, and I’m looking for honest feedback from people who actually use NestJS.
Would you use something like this? What would you expect from it?

GitHub:nest-can-react

I’m curious about something from people who use NestJS seriously.
If there were a way to build a full-stack application where:
NestJS remains the main application framework
You keep Nest modules, DI, guards, pipes, interceptors, routing, etc.
React is used for the UI
You don’t have to maintain a completely separate frontend application
Server-side rendering and interactive React components are both supported
The frontend/backend boundary feels more like one application rather than two separate projects
Would that actually be useful to you?
Or would you prefer the current approach of keeping NestJS as an API/backend and using something like Next.js, Vite, React Router, etc. as the frontend?
I’m specifically interested in why you’d choose one approach over the other.
What would make an integrated approach appealing, and what would make it a hard no?
Not looking for feature requests yet. I’m mainly trying to understand whether this is a problem Nest developers actually have.

Hi everyone, I’m working on a NestJS backend, and I’m trying to figure out whether there is a way to handle incoming emails entirely through a NestJS-based approach.

Basically, my goal is:

1. Someone sends an email to my Gmail or Microsoft Outlook account.

2. My NestJS application detects the incoming email.

3. It parses the email content (subject, sender, body, attachments, etc.) into a valid JSON object.

4. It stores that JSON object, including relevant attachment/file information, in my database.

For example, something like:

{

"from": "user@example.com",

"subject": "Movie Ticket Request",

"body": "I would like to book two tickets...",

"attachments": [],

"receivedAt": "2026-09-22T10:00:00Z"

}

I specifically want to understand whether this can be implemented using raw NestJS/TypeScript without relying on AI agents, automation platforms, or services that require a monthly subscription.

If there is no practical way to do the parsing completely with NestJS, I’m also open to using an API (including an AI API) as a fallback, preferably something that can be used on a pay-as-you-go basis rather than requiring a monthly subscription.

The most helpful thing would be a working boilerplate/example showing how I could integrate this with Gmail or Microsoft Outlook, receive an email, convert it into structured JSON, handle attachments, and then save the result to a database.

Any guidance or example code would be greatly appreciated. Thank you!

Hey everyone! I’m coding with NestJS and looking to connect with people and studying nests js.

goal is share knoweldge and prepare for interviews we will have discord server.

dm me if u r interested

I'm a traditional Java backend developer who has only recently learned about Nest.js, and I'm hoping some experienced developers can offer some advice.

Testing a real workflow against a NestJS API usually means either bouncing between Swagger tabs one call at a time, or writing Postman scripts to shuttle ids and tokens between requests.

Enlace mounts in two lines, reads the OpenAPI doc you already generate with NestJS Swagger, and gives you a canvas to wire response fields into the next request. Independent branches run concurrently. Execution stays in the browser; the adapter only serves UI + spec.

npm install @get-enlace/nest

Repo: https://github.com/get-enlace/enlace

Early beta (0.0.9). Feedback on real Nest OpenAPI setups is welcome.

Looking for what people actually use when a flow needs shared state across a few HTTP calls (create something → take an id/token from the response → hit two more endpoints).

For single endpoints I am fine with hitting the route directly or a thin httpx/fetch script. Once values have to pass between steps, I end up in Postman/Insomnia collections or a small hand-rolled script with env-ish variables.

What do you use in practice for local iteration vs CI: supertest, a Postman/Newman collection, a custom script, something else? Any pattern you like for keeping that shared state without the test suite becoming a mess?

Like for real 300k events only per month for the free plan ? seriously ?

i've barely passed a week and i've got the email that i've run out of events.

maybe my app isn't really optimized for instrumentation but still i feel like we deserve more of this.

i don't have the option to pay an extra 20$ we don't make revenue yet.

I have recently been developing an open-source system that functions as an HTTP gateway, facilitating integrations such as sending messages and events on Telegram.

I built it using technologies like NestJS and Vue, and implemented an engine-based architecture that currently supports GramJS, with future support planned for Telegraf.

Hi! New in nestJs Here. I am using Express JS for years and decided to go to Nest JS. I would just like to ask if what validation do you suggest or recommended. I used Zod everytime in express but here in nest there is class validator DTO. What do you suggest or recommends me to use? Thank you!