r/nestjs • • Feb 19 '25

Looking for an early stage BE engineer

0 Upvotes

Hi all,

A few months ago, I identified a need in the field services industry. So I've built a niche platform to target lawn treatment companies. The long term vision is that a new company can signup for our SaaS and that's it. Their company has been started. They can create and host their website, manage inventory, manage employees(likely a HRIS api instead of building out payroll and other HR features), crew tracking, NPS integration, compliance, a help desk ticketing system, and really whatever else our users and research determine is needed.

In it's current state, it handles operations, billing, and a light CRM. Very much a MVP approach so we can learn from the early adopters. I'm around 95% done with the MVP but that is just 0 to 1. I need to also take it from 1 to many features.

What I'm looking for:

Someone to primarily assist with the BE work. The stack currently includes Nestjs, TypeORM, Postgres, Typescript, Azure, Azure Devops, Firebase Auth, Sendgrid, Stripe, and Twilio. Someone who truly enjoys SQL and BE architecture would really balance out the company. I need someone who requires little oversight, is detail oriented, and enjoys the hustle/grind. I'm happy to do standups, refinements, and whatever else we decide on, but the bulk of communication will be async.

A plus would be someone who can work fullstack(nextjs & MUI) and is also familiar with Bicep or Terraform.

A bit about me:

I've been an engineer for the past 8ish years. I've mostly done fullstack work with a focus on the FE as that's what I enjoy. I've continued to level up and my current title is staff software engineer. I also have experience leading sales teams and have worked in marketing.

Compensation:

A pure equity arrangement would be ideal. I know leaving it at that in a post is sus. A part time hourly + equity arrangement is a more realistic expectation from my end. The company is bootstrapped fwiw.

If interested:

Don't just hit me with an "I'm interested, send a DM". Let me know your background, and whatever else may be helpful.


r/nestjs • • Jun 08 '26

PSA: pnpm 11 silently breaks bcrypt (and other native modules) in Docker builds

0 Upvotes

If you upgraded to pnpm 11 and your deploys started failing with `ERR_PNPM_IGNORED_BUILDS`, here's what happened.

pnpm 11 enables `strictDepBuilds` by default. Native modules like bcrypt, sharp, argon2 have build scripts that compile C++ binaries during install — pnpm now blocks these unless explicitly allowed.

The tricky part is Docker. The instinct is to add `--ignore-scripts` to silence the error. Don't. That skips compilation entirely and trades a build-time failure for a runtime crash when your app actually tries to use bcrypt.

Two more things that collide with this at once:

- Your `prepare` script (usually husky) blows up in a `--prod` install once `--ignore-scripts` is gone

- pnpm 11 requires Node 22. It won't run on Node 20 at all (`node:sqlite` isn't available)

The fix is three parts: inject `dangerouslyAllowAllBuilds` into `pnpm-workspace.yaml`, delete the `prepare` script before install, and make sure you're on Node 22.

Wrote up the full breakdown with a working Dockerfile if anyone needs it let me know in the comment .


r/nestjs • • Sep 22 '26

NestJS: How to Automatically Parse Incoming Gmail/Outlook Emails into JSON and Store Them in a Database

0 Upvotes

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": "[email protected]",

"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!


r/nestjs • • May 28 '26

process.env is killing your performance and here is why .

0 Upvotes

When you run process.env.envName.
under the hood three things happen

  • System Calls: Unlike regular JavaScript objects, process.env is not a standard object. Accessing it often triggers native C++ code to query the operating system's environment variables.

  • String Casting: Every time you read a value from process.env, Node.js must cast it into a string, adding extra overhead.

  • No Native Caching: In some Node.js versions, the runtime reads from the system environment every time you access the property rather than caching the result .

nestjs come with the @/nestjs``/config and thats a huge improvement . over process.env however it's syntacticaly unsanitary to read and transform at the service layer .

You'd normally use it like so .

import { Module } from '@nestjs/common';
import { ConfigModule } from '@nestjs/config';


@Injectable() 
export class UsersService { 
constructor(private configService: ConfigService) {} 

getDatabaseUrl(): string { 

// Fetches from process.env, with optional fallback value return this.configService.get<string>('DATABASE_URL', 'mongodb://localhost:27017'); 

} 
}

The best practice however is to have a typed configFile that you can easily pass around and inject into your service layer effortlessly data stays on the heap longer and you won't to gauge your eyes out everytime you reference an environemt variable .

export default () => ({ 
port: parseInt(process.env.PORT, 10) || 3000, database: { host: process.env.DATABASE_HOST, port: parseInt(process.env.DATABASE_PORT, 10) || 5432, }, 

});

Load it

ConfigModule.forRoot({ load: [configuration], });

import { Injectable, Inject } from '@nestjs/common';
import { ConfigType } from '@nestjs/config';
import configuration from './config/configuration';

@Injectable()
export class DatabaseService {
  constructor(
    (configuration.KEY)
    private dbConfig: ConfigType<typeof configuration>,
  ) {}

  getDbHost() {
    return this.dbConfig.database.host;
  }
}

r/nestjs • • Feb 21 '26

I implemented a Clean Architecture + CQRS pattern in NestJS 11. I’m looking for feedback on this folder structure. 🏗️

3 Upvotes

After 60+ hours of engineering, I’ve completed a production-grade foundation. I wanted to see how far I could push DX using Biome and Better Auth.

Key features implemented:

  • CQRS Pattern: Complete separation of Commands and Queries.

  • Event-Driven: Decoupled side effects using an internal event bus.

  • Better Auth: Type-safe sessions, OTP, and RBAC.

  • Biome: Replaced ESLint/Prettier for 100x faster linting.

  • Tests: 327+ tests (Unit, Integration, and E2E).

I've open-sourced a Demo version here so you can audit the architecture: 🔗 [GitHub Demo]

I’d love to hear your thoughts on how you handle Domain Events in NestJS. Does this approach look solid to you?


r/nestjs • • Oct 09 '24

Moving From Expressjs to Nestjs

0 Upvotes

r/nestjs • • Feb 03 '25

Help

0 Upvotes

I use swagger, but mi method register its blocked by CORS, i put available cors, but dosnt work


r/nestjs • • Mar 10 '26

Do you add hyperlinks to your REST API responses?

0 Upvotes

I've been thinking about this lately while working on a NestJS project. HATEOAS — one of the core REST constraints — says that a client should be able to navigate your entire API through hypermedia links returned in the responses, without hardcoding any routes.

The idea in practice looks something like this:

{
  "id": 1,
  "name": "John Doe",
  "links": {
    "self": "/users/1",
    "orders": "/users/1/orders"
  }
}

On paper it makes the API more self-descriptive — clients don't need to hardcode routes, and the API becomes easier to navigate. But in practice I rarely see this implemented, even in large codebases.

I've been considering adding this to my NestJS boilerplate as an optional pattern, but I'm not sure if it's worth the added complexity for most projects.

Do you use this in production? Is it actually worth it or just over-engineering?


r/nestjs • • May 15 '24

NestJS gives vibe low code

1 Upvotes

I've been diving deeper into NestJS lately and something intriguing stood out to me about its architecture—particularly its extensive use of decorators. It's made me think: does NestJS inadvertently bring us into a low-code territory?


r/nestjs • • Apr 18 '25

Why Nest over Nuxt?

0 Upvotes

For those of you who have looked into or used Nuxt, what keeps you using Nest.js instead? I prefer having a separate backend, but curious what yours is


r/nestjs • • Oct 03 '26

FOR HIRE Junior Backend / Full-Stack Developer | NestJS, ASP.NET Core, PostgreSQL, Next.js | Bangladesh / Remote

0 Upvotes

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:

[email protected]

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


r/nestjs • • Apr 05 '23

Would you pay for a Nest js Graphql boilerplate? A startup kit that includes Auth, Validation, DB integration, migrations and more?

0 Upvotes

Hello,

It's really annoying to spend like 1-2 months writing all the boilerplate necessary in every nests project, so I thought that it will be useful to create one.

Would you pay for it? How much do you think it's fair?

Thanks.


r/nestjs • • Aug 04 '26

Built a multi-tenant workflow engine with NestJS + BullMQ + DLQ – looking for architecture review

Thumbnail reddit.com
0 Upvotes

r/nestjs • • Sep 22 '26

Can NestJS become a full-stack framework?

6 Upvotes

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


r/nestjs • • May 17 '25

Nesjts Udemy Course

0 Upvotes

Hey my new course is about nestjs

You can acces with coupon code here;
https://www.udemy.com/course/from-to-the-end-nestjs/?couponCode=F42F8385FD0D0931E72E


r/nestjs • • Oct 14 '25

NexusAuth? Have you heard of this new NPM package?

0 Upvotes

Hello, It is difficult to publicise any type of project created by oneself on Reddit communities, obviously because many people would use it to promote themselves.

The NexusAuth package was created by user SebastiaWeb. It is open source, and the aim is for people to test its features, start creating patches, and correct the documentation to make it clearer for the community.

It has different adapters that make it lighter than other libraries. Another advantage is that you can map your existing database without deleting it.

✨ Why NexusAuth?

Stop fighting with authentication libraries that force you into their way of doing things. NexusAuth adapts to your project, not the other way around.

  • 🏗️ Framework Agnostic: Works with Next.js, NestJS, Express, or vanilla Node.js. You choose.

  • Any Database: TypeORM, Prisma, Mongoose, SQL — or bring your own. Hexagonal architecture FTW.

  • 🔐 OAuth Ready: Google, GitHub, Facebook, Microsoft providers out of the box. More coming.

  • 📦 Monorepo Structure: Install only what you need. No bloat, just focused packages.

If you believe in open-source projects, give them a star on GitHub.

The link to view it is:

https://github.com/SebastiaWeb/nexus-auth/blob/master/README.md

https://www.npmjs.com/search?q=nexusauth

If you have any questions, please post them in the comments section and I will respond.


r/nestjs • • May 09 '26

How to share a single Prisma client instance between a NestJS app and a plain Node.js app in a pnpm monorepo?

1 Upvotes

I have a pnpm monorepo with two apps a NestJS API and a Node.js scraper both using Prisma 7. I want a single PrismaClient instance defined in a shared /myapp/database package so both apps use the same configuration and connection setup.

#folder structure
apps/
  api/          # NestJS app
  node-app/      
packages/
  database/
    src/
      generated/prisma/   
      index.ts            # exports prisma instance + types
    prisma/
      schema.prisma
    package.json
package.json

#packages/database/src/index.ts:
 
import { PrismaPg } from '@prisma/adapter-pg';
import { PrismaClient } from './generated/prisma/client.js';

const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL! });

export const prisma = new PrismaClient({ adapter });

export * from './generated/prisma/client.js';
, 

The nodejs app imports it directly, no issues. The problem is NestJS the standard pattern is to extend PrismaClient in an Injectable() service, which creates a second instance alongside the one already created in the shared package.

is it actually a problem to have two separate PrismaClient instances here (one per app process)? Since the scraper and API run as separate processes If it is a problem, how do I wrap the existing singleton so NestJS's DI system uses it without creating a new one?

Injectable()
export class PrismaService {
  // somehow wrap/expose the shared singleton here
}

Also, please don’t say “ask AI.” I did, and I’m not sure about its answers. I don’t want to blindly follow it, as this is a strictly no-AI project to improve my knowledge since I’m still a junior developer.


r/nestjs • • Jun 24 '26

Is NestJS actually niche/rarely used in 2026, or is this outdated info?

7 Upvotes

Got some advice recently that NestJS "isn't industry standard" and "barely anyone uses it" anymore, especially compared to other backend frameworks. This didn't match what I'd researched myself, so wanted a reality check from people actually building with it.

For context — I'm evaluating a SaaS platform built on NestJS 11 + TypeScript + TypeORM + PostgreSQL, and trying to figure out if that was a reasonable tech choice or something I should be worried about going forward.

Is NestJS genuinely fading in adoption, or is this just someone's personal bias/lack of exposure to it? Curious what people actually building production backends are seeing in the field right now.


r/nestjs • • May 18 '25

Production-Grade Node.js Auth Template (Postgres/MongoDB, TS/JS)

5 Upvotes

Sharing my open-source authentication template, built to save you from reinventing the wheel on auth for every new Node.js project. It's designed to be a secure, scalable, and feature-rich starting point.

Core Stack (latest branch): Node.js, Express, Neon/Postgres (with Drizzle ORM), Redis, RabbitMQ.

Key Features:

  • Full JWT auth (access/refresh tokens, rotation)

  • Email verification & secure password reset

  • Account confirmation flows

  • Session management with Redis

  • Async tasks via RabbitMQ (e.g., emails)

  • Factory patterns for DRY code (repository, service layers)

  • Docker setup for dev/prod

  • Integrations: S3, Razorpay, Resend (for emails)

  • Monitoring: Prometheus/Grafana stubs

  • DB migrations & cron jobs

Available Branches to suit your stack:

  • `ts-postgres` (Drizzle ORM)

  • `ts-mongoDB` (Mongoose)

  • `js-mongoDB` (Mongoose)

The goal is to provide a solid foundation with best practices baked in, so you can focus on your app's unique features.
Check it out:- Check here


r/nestjs • • Apr 21 '24

Why nest js is hard to learn?

0 Upvotes

I am new to nestjs and I find it so difficult to learn. Can you guys recommend me some easy tutorials, docs, resources to learn it?


r/nestjs • • Apr 05 '26

@relayerjs/nestjs-crud - Full-featured REST CRUD for NestJS with Drizzle ORM

2 Upvotes

Hey NestJS devs!

I built @relayerjs/nestjs-crud - a package that aims to turn your Drizzle schema into a full featured REST CRUD.

The pain points I tried to solve are reducing boilerplate when building a flexible API, and providing good support for computed/derived and JSON filtering.

In the Model you can define a number of fields that are calculated in SQL at runtime and can be filtered, sorted, and aggregated in the API just like regular columns.

Quick example:

@CrudController<PostEntity, EM>({
  model: PostEntity,
  path: 'blog-posts', 
  id: { field: 'id', type: 'uuid' },

  routes: {
    list: {
      pagination: 'offset',  
      defaults: { 
         // override select, where & default sorting
      },
      allow: {
        select: { title: true, comments: { $limit: 5 } },
        where: {
          title: { operators: ['contains', 'startsWith'] },
          published: true,
        },
        orderBy: ['title', 'createdAt'],
      },
      maxLimit: 100,
      defaultLimit: 20,
      search: (q) => ({
        OR: [{ title: { ilike: `%${q}%` } }, { content: { ilike: `%${q}%` } }],
      }),
    },
    findById: true,
    create: { schema: createPostSchema },
    update: { schema: updatePostSchema },
    delete: true,
    count: true,
    aggregate: true,
  },
  swagger: {
    tag: 'Blog Posts',
    list: { summary: ‘Blog posts', description: ‘Posts with search and filters' },
    // … other endpoints
  },
})
export class PostsController extends RelayerController<PostEntity, EM> {
  constructor(postsService: PostsService) {
    super(postsService);
  }
}

This will give you full CRUD endpoints with powerful filtering & searching, relation management and aggregations API + Swagger documentation.

The package is built on top of my other package called Relayer, that encapsulates the querying engine.

Currently supports Drizzle ORM only, because it’s just my favorite one, but I have some work in progress on adding Kysely & MikroORM and maybe some more later if anyone is interested.

Docs available here: https://relayerjs.vercel.app/nestjs/getting-started

Repo: https://github.com/awHamer/relayer

There's an example app in the repo.

I’d be glad to hear any feedback, thank you!


r/nestjs • • May 05 '26

Seeking Nestjs , React/Reactnative devs who have dealt with delivery apps before for a job .

1 Upvotes

r/nestjs • • Feb 07 '24

全栈开发者(TS, React, Vue, NestJs) 求职远程工作/外包接单

0 Upvotes

个人介绍

本人13年开始学习Object-C, 毕业之后长期从事iOS端的App开发,在工作期间写过Android,PHP。有CRM, 门户网站, 电商系统, ERP系统,小程序等经验。18年转技术栈为React,TS和Node.js,目前在工作中主要技术栈以Vue为主,外包业务以Nest.js+React+Vue为主,也承接过Java外包。会一些轻量级的CI/CD(比如drone,jenkins)等等。

期望得到一份以个人开发为主,不需要频繁开会的远程工作,全职和兼职都可以,或者承接长期稳定的外包业务

个人网站:阿甘的小站

主要技术栈

  • react,vue

  • typescript,node.js,nestjs, typeorm等

  • java,uniapp,小程序等

  • drone,linux,mysql,springboot,docker,jenkins,reids,cicd等

基本要求

  • 外包442付款

  • 长期远程、兼职、坐班都可以接受

  • 远程工作薪资不讲究,差不多即可

项目

一、Vue + Java + mysql + SpringBoot的一个商城管理系统, 包含了SKU管理, SPU管理, 广告管理,优惠券管理等等

前端源码: https://gitlab.com/xxbarca/wx_mall_admin

后端源码: https://gitlab.com/xxbarca/wx_mall_admin_api

在线预览: http://124.221.1.101:3304/#/

二、商城项目小程序端, 后端使用了java, 实现了商品详情,购物车,sku的选择等基础功能

技术栈:

  • 原生小程序

  • Java

  • mysql

  • JPA

后端源码:https://gitlab.com/xxbarca/wx_mall_api

小程序源码:https://gitlab.com/xxbarca/wx_mall

三、一款NestJs +Vue 编写的一款前后端分离大学校园社交项目,包含用户管理,角色管理,菜单管理,部门管理,系统监控等功能

技术栈:

  • NestJs

  • Vue

  • mysql

  • TypeOrm

前端源码:https://gitlab.com/xxbarca/youni_admin

后端源码:https://gitlab.com/xxbarca/youni_api

在线预览:http://124.221.1.101:3305

四、折扣网站

技术栈:

  • NestJs

  • React

  • mysql

  • TypeOrm

前端源码: https://gitlab.com/xxbarca/goflash_admin

后端源码:https://gitlab.com/xxbarca/goflash_api

在线预览:http://124.221.1.101:3303

其他项目:

  • 华行大数据(react+java)

  • 汽车之家后台管理系统(java+vue)

  • 汽车之家后台管理系统(java+vue)

  • 汽车之家小程序(uniapp)

  • 汽车之家推广小程序(uniapp)

  • 大数据云平台(java+vue+websocket+echarts+高德地图)

  • 慧居时代收费系统(react+java)

  • 智能工厂(angular+java)

  • 全周期健康管理系统(nestjs+react)

  • 全周期健康小程序(nestjs+uniapp)

  • 优谷工单管理系统(iOS,Android)

...

欢迎联系我:

微信:liyangly1217

qq: 3767061187

email: [email protected]


r/nestjs • • Jul 26 '24

Expecting Something more from Nestjs

1 Upvotes

Okay, I am a freelancer working on some projects, A mid level project, as I have been assigned to rewrite and refactor some of their code which will help them to migrate services from, So being in nestjs domain since long like 2022, But what I fill is that if they want to play good, and remove the tag "it is built on the top of expressjs" Then they should try something in new like hono which using bun runtime, and this way faster than regular express js and they also gain popularity, stability and connectivity.