NestJS Best Practices (Yet another Claude skill)

DayTradingCentral – Free Trading Journal (Next.js, NestJS, Postgres)

I’m a Computer Engineering student from Brazil. I built this to showcase backend patterns that go beyond simple CRUDs: row-level multi-tenancy (Prisma), async processing (BullMQ&#x2F;Redis), and observability (OpenTelemetry). Looking for feedback on the architecture!

Show HN: Production-Ready NestJS Back End (Multi-Tenancy, Event-Driven)

Osprey API Tester – API testing inside VS Code for NestJS projects.It reads NestJS controllers and DTO classes to:list available routesparse route params, query params, and headersgenerate request URLs from decoratorsgenerate JSON bodies from DTOsallow sending requests directly from VS CodeNo runtime dependency on the server.
Uses TypeScript AST (ts-morph).
Limitations: NestJS + TypeScript only.

Show HN: Osprey API Tester – VS Code API Testing from NestJS Controllers/DTOs

I&#x27;ve spent the last few months working on something I wish I&#x27;d had years ago.
I kept running into the same issue: CI green, production mail broken. TLS handshake failures, DKIM alignment mismatches, SPF soft-fails ... the stuff that only surfaces when real mail servers are involved.
Most test tools (Mailpit, MailHog) are catch-alls. They confirm &quot;an email was sent&quot; but don&#x27;t validate the protocol. They also aren&#x27;t designed for network-exposed environments: no auth, unprotected Web UI, easy to enumerate messages.VaultSandbox is my attempt at fixing that.
It&#x27;s a self-hosted SMTP gateway (AGPLv3) that validates SPF, DKIM, DMARC, and rDNS on every incoming message. You keep your production email provider (Postmark, SendGrid, SES) in tests and you just change the recipient domain. No mocking, no config changes.
There are client SDKs (Node, Python, Go, Java, .NET), plus a Web UI and a CLI for manual testing.Some technical details:Deterministic Tests
Instead of polling or sleep loops, the SDKs use Server-Sent Events (SSE) so test assertions trigger the moment the mail hits the gateway.Minimal infrastructure footprint
Built with NestJS and Angular, with no external database dependency to keep the container footprint small and easier to reason about.Post-Quantum Encryption
I use ML-KEM-768 for the encryption layer. Incoming mail is encrypted immediately using a client-generated public key and the plaintext is discarded. The server only ever stores encrypted message data and cannot decrypt it. I chose PQ because I wanted to build something I wouldn&#x27;t have to revisit in five years. If it handles large PQ keys reliably, everything else is easy.Quick start:
<a href="https:&#x2F;&#x2F;vaultsandbox.dev&#x2F;getting-started&#x2F;quickstart&#x2F;" rel="nofollow">https:&#x2F;&#x2F;vaultsandbox.dev&#x2F;getting-started&#x2F;quickstart&#x2F;</a>Site:
<a href="https:&#x2F;&#x2F;vaultsandbox.com" rel="nofollow">https:&#x2F;&#x2F;vaultsandbox.com</a>I&#x27;d love feedback, especially on whether AGPLv3 would be a blocker for something you&#x27;d self-host in dev.

Show HN: VaultSandbox – Test your real MailGun/SES/etc. integration

I recently ran an audit on our latest full-stack repo to figure out why &quot;spinning up a new project&quot; felt like such a heavy lift. I counted every file required just to reach a &quot;production-ready&quot; baseline—before writing a single line of unique feature code.The count was roughly 600 files.To be clear, I&#x27;m not talking about a `create-react-app` sandbox. I mean a compliant, scalable SaaS foundation: Next.js frontend, Node.js&#x2F;NestJS backend, mobile wrapper, CI&#x2F;CD pipelines, and enough security config to pass a SOC2 audit.It sounds ridiculous (and honestly, it feels ridiculous), but when I broke it down, I couldn&#x27;t find many files I was willing to delete.Here is where the bloat comes from:First, the &quot;Configuration Hell&quot; accounts for about 40-50 files alone. We aren&#x27;t just dealing with `package.json` anymore. It&#x27;s `tsconfig.json` (base), `tsconfig.build.json`, `tsconfig.spec.json`... multiplied across frontend, backend, and shared libraries. Then add `.eslintrc.js`, `.prettierrc`, `jest.config.js`, `vitest.config.ts`, `nodemon.json`, and the Docker-compose variants for dev, test, and prod.Then there’s the DevOps and Quality layer. We have roughly 20-30 files for GitHub Actions workflows (lint, test, build, deploy, semantic release), Husky hooks (pre-commit, commit-msg), and pull request templates.But the real multiplier is the separation of concerns. In a modern monorepo, a &quot;Hello World&quot; isn&#x27;t just `console.log`. It’s:
- A NestJS module (Controller, Service, Module, DTO, Entity, Unit Test, E2E Test).
- A Next.js slice (Page, Component, Type definition, API client wrapper).
- A shared library entry.We found that adding a single &quot;minimal&quot; API endpoint usually touches 5-7 files just to maintain architectural standards.The trade-off is painful. On one hand, this setup handles the things we used to forget: security headers, proper logging, consistent error handling, and type safety across boundaries. It prevents the &quot;spaghetti code&quot; distinct to startups that scale too fast.On the other hand, the cognitive load of managing a 600-file &quot;empty&quot; project is massive. Updating dependencies becomes a chore because a major version bump in one tool (like ESLint) cascades through forty config files.I’m curious how others are handling this &quot;starting line&quot; complexity.Are you accepting the boilerplate as the cost of doing business? Or have you found a way to strip this down without sacrificing the compliance&#x2F;safety guardrails that enterprise clients demand?It feels like we&#x27;ve over-engineered the entry point of software development, but I’m not sure what the alternative is for a serious project. We tried going &quot;lean&quot; initially, but spent weeks retrofitting auth and testing harnesses later—which was worse.Is there a middle ground I&#x27;m missing, or is ~600 files just the new normal?

Tell HN: A production-ready "Hello World" is now ~600 files

Hi HN,I built ProjectCLI (@dawitworku&#x2F;projectcli) — a universal interactive CLI for developers who are tired of juggling multiple project generators.Problem:
Setting up a new project often requires learning dozens of commands: create-react-app, cargo new, poetry new, laravel new, etc. It’s tedious, error-prone, and repetitive.Solution:
ProjectCLI lets you scaffold *any project in minutes*:
- Multi-language support: JS, TS, Python, Rust, Go, Java, PHP, C#, Dart, Swift, Ruby.
- Multi-framework support: React, Next.js, Vue, NestJS, Express, Django, Flask, Actix, Axum, Rocket, Laravel, Symfony, Spring Boot, etc.
- Interactive CLI with fuzzy search, smart defaults, and context awareness.
- Preflight checks for missing tools.
- Remote templates: clone any GitHub starter kit for instant scaffolding.
- One-click CI&#x2F;CD &amp; Docker setup.
- Non-interactive mode for automation or scripts.Quick Start:
```bash
npx @dawitworku&#x2F;projectcli@latest
# or globally
npm install -g @dawitworku&#x2F;projectcli
projectcli
 Why I built it:
I wanted a single tool that works across languages and frameworks, saves hours, and makes project bootstrapping fun and reliable.GitHub: https:&#x2F;&#x2F;github.com&#x2F;Dawaman43&#x2F;projectcliNPM: https:&#x2F;&#x2F;www.npmjs.com&#x2F;package&#x2F;@dawitworku&#x2F;projectcli

ProjectCLI: The Swiss Army Knife CLI for bootstrapping any project

Hi HN,I’ve been working on Rikta, a backend framework for Node.js designed to make building scalable TypeScript applications more intuitive and modular.After working with various Node frameworks, I felt there was a need for something that strictly enforces modularity and provides powerful out-of-the-box integrations without the &quot;magic&quot; that often makes debugging difficult.What is Rikta?
Rikta is a collection of packages designed to work together seamlessly. It’s built around a core that handles the application lifecycle and dependency injection, allowing you to plug in exactly what you need.Key Features:Zero-Config Autowiring No imports: [], exports: [], or providers: [] arrays. Just decorate your class, and it works.Fastify Powered: Built on top of Fastify for maximum performance and low overhead. Rikta is 32% faster than NestJS on average.Built-in TypeScript Support: Developed in TS for TS. You get full type safety across your entire backend stack.First-class Integrations: Native support for TypeORM (database) and Swagger (automatic API documentation) via @riktajs&#x2F;typeorm and @riktajs&#x2F;swagger.Developer Experience: A dedicated CLI (@riktajs&#x2F;cli) to scaffold components and manage the project structure efficiently.Lightweight Core: The core remains lean; you only add the features your specific application requires.Why I&#x27;m building this:
The goal of Rikta is to bridge the gap between &quot;unstructured&quot; Express apps and &quot;overly complex&quot; enterprise frameworks. I wanted a developer experience that feels fast but results in a codebase that a team can maintain for years.Looking for Feedback &amp; Collaborators:
The project is currently in its early stages, and I’m looking for the HN community to help shape its direction. I’d love to hear your thoughts on:The modularity pattern and Dependency Injection implementation.The integration of Swagger&#x2F;OpenAPI as a default.What&#x27;s missing in your current Node.js backend workflow that Rikta could solve?Documentation is available at rikta.dev. I&#x27;m looking forward to your critiques and suggestions!

Show HN: Rikta – A modular, TypeScript-first back end framework for Node.js

After my annual checkup showed LDL 4.4 mmol&#x2F;L (170 mg&#x2F;dL) and triglycerides 
2.0 mmol&#x2F;L at 33, I tried tracking with ChatGPT (lost data when context got 
too big), then spreadsheets (too tedious).Built a simple tracker focused on cholesterol. Log meals, see lipid breakdown, 
track trends. I believe snacks and sugar were my main issue.Stack: Angular 17 + NestJS + SupabaseStarted January 1st, already lost 3kg. Same breakfast daily (psyllium, oats, 
chia, skyr, whey, berries), cut sugar from daily to once per week.Free during beta. Looking for feedback on whether strict diet cutting or 80&#x2F;20 
approach is more sustainable long-term.

Show HN: Cholesterol Tracker – Built after high cholesterol diagnosis at 33

I built DreamStack because I was tired of the &quot;disposable MVP&quot; culture in Node.js. Most templates&#x2F;starters tie your business logic so tightly to Express or NestJS that a framework migration is effectively a total rewrite.I wanted to see if I could build a truly agnostic engine using the Adapter and Repository patterns.
The Result:Framework Agnostic: You can swap the underlying HTTP engine (Express ↔ Hono) via a single .env variable.A+ AI Audit: I used GitHub Copilot to perform a modularity audit, which returned a 98&#x2F;100 score on separation of concerns.Performance-First Testing: I optimized the DI container and persistence layers so that all 508 tests (unit + integration) run in under 10 seconds.Infrastructure Flexibility: Swappable layers for SQL (Prisma) and NoSQL (Mongoose).It includes the &quot;boring stuff&quot; like JWT rotation, RBAC, and OAuth so you can focus on the unique parts of your app. I&#x27;m here to talk about the architectural trade-offs of this approach versus the standard &quot;batteries-included&quot; frameworks.

Show HN: DreamStack – Framework-agnostic Node.js foundation - 500+ tests (~10s)

I spent 4 years trying to build this OAuth server but never finished it.Then I discovered agentic coding and shipped it in 3 weeks.What makes it different:• Dual AI agents analyze every login in &lt;300ms
 - Security Signals Agent: risk scoring (device, IP, geo, velocity)
 - Policy Compliance Agent: business rules (MFA policies, role enforcement)
 - Combined decision: allow&#x2F;log&#x2F;step-up&#x2F;lock&#x2F;deny• Production-ready security
 - PKCE (RFC 7636), DPoP (RFC 9449)
 - MFA (TOTP + WebAuthn&#x2F;Passkeys)
 - IP restrictions, rate limiting, audit trail• EU digital sovereignty
 - GDPR native (data export, legal holds, retention policies)
 - EU hosting, no US Cloud Act exposure
 - Full audit trail (PostgreSQL + Redis Streams)• Zero AI dependency
 - Deterministic fallback if AI timeouts
 - Conservative MEDIUM risk returned (safe default)
 - System keeps running without external LLM calls• Modern stack
 - Backend: NestJS + TypeScript, LangChain&#x2F;LangGraph
 - Frontend: React 19, hexagonal architecture, 91% test coverage
 - Deterministic fallback if AI timeouts (zero dependency)Built as an alternative to Firebase Auth &#x2F; AWS Cognito &#x2F; Auth0 for companies that want control over their authentication infrastructure.Architecture diagrams and screenshots in the repo.Open to feedback and questions.

Show HN: OAuth 2.0 server with AI security agents (EU sovereign alternative)

Hello Hacker News — greetings from South Korea 
I’m a backend engineer working primarily with Go, and I’d like to share a framework I’ve been building to solve a problem I’ve repeatedly encountered in production systems.In my day-to-day work, our backend is built on top of Echo. Echo is fast and reliable as an HTTP transport, but its high level of freedom leaves architectural decisions almost entirely to individual developers. Over time, this led to a system where execution flow and responsibility boundaries varied depending on who last touched a feature. Maintenance became difficult not because the code was incorrect, but because how requests actually executed was no longer obvious.I looked for a Go framework that could provide a clear execution model and structural constraints, similar to what Spring or NestJS offer. I couldn’t find one that fit. Moving to Spring or NestJS would also mean giving up some of Go’s strengths—simplicity, performance, and explicit control—so I decided to build one instead.Spine is an execution-centric backend framework for Go.
It aims to provide enterprise-grade structure while deliberately avoiding hidden magic.What Spine provides
 • An IoC container with explicit, constructor-based dependency injection
 • Interceptors with well-defined execution phases (before, after, completion)
 • First-class support for both HTTP requests and event-driven execution
 • No annotations, no implicit behavior, no convention-driven wiringThe core idea: execution firstThe key difference is Spine’s execution model.Every request—HTTP or event—flows through a single, explicit Pipeline.
The Pipeline is the only component that determines execution order.
Actual method calls are handled by a separate Invoker, keeping execution control and invocation strictly separated.Because of this structure:
 • Execution order is explainable by reading the code
 • Cross-cutting concerns live in the execution flow, not inside controllers
 • Controllers express use cases only, not orchestration logic
 • You can understand request handling by looking at main.goThis design trades some convenience for clarity. In return, it offers stronger control as the system grows in size and complexity.My goal with Spine isn’t just to add another framework to the Go ecosystem, but to start a conversation:
How much execution flow do modern web frameworks hide, and when does that become a maintenance cost?The framework itself is currently written in Korean.
If English support or internationalization is important to you, feel free to open an issue—I plan to prioritize it based on community interest.You can find more details, a basic HTTP example, and a simple Kafka-based MSA demo here:
Repository: <a href="https:&#x2F;&#x2F;github.com&#x2F;NARUBROWN&#x2F;spine" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;NARUBROWN&#x2F;spine</a>Thanks for reading. I’d really appreciate your feedback.

Show HN: Spine – an execution-centric backend framework for Go

Hi HN,We built Supercheck – an open source platform that combines test automation and uptime monitoring in one self-hosted solution.*The Problem:*
Most monitoring tools are expensive SaaS products that charge per check. Test automation and monitoring are often separate concerns, using different tools and workflows. We wanted a unified platform where you can write a Playwright test once and use it for both CI&#x2F;CD testing and production monitoring and use same tool for k6 performance tests too.*What Supercheck Does:*Testing:
- Playwright browser tests (UI&#x2F;E2E) with screenshots, traces, videos
- API tests (HTTP&#x2F;GraphQL)
- Database tests (PostgreSQL, MySQL)
- k6 performance tests
- Schedule tests via cron or trigger from CI&#x2F;CDMonitoring:
- HTTP, Website, Ping, Port monitors
- Synthetic monitors (run full Playwright tests on a schedule)
- Multi-region: US East, EU Central, Asia Pacific
- Threshold-based alerting (consecutive failures before alerting)Extras:
- AI Create: Generate tests from plain English
- AI Fix: Automatically analyze failures and suggest fixes
- Public status pages with incident management
- Alerts: Slack, Discord, Telegram, Email, Teams, webhooks
- RBAC with 6 permission levels
- Browser extensions: Chrome + Edge*Architecture:*
Next.js frontend, NestJS workers, PostgreSQL, Redis + BullMQ for job queuing, MinIO for artifacts. Each browser test runs in an isolated Playwright context. Workers are stateless – scale horizontally by adding more containers.*Deploy:*
```bash
git clone <a href="https:&#x2F;&#x2F;github.com&#x2F;supercheck-io&#x2F;supercheck" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;supercheck-io&#x2F;supercheck</a>
cd supercheck&#x2F;deploy&#x2F;docker
.&#x2F;init-secrets.sh
docker compose -f docker-compose.yml up -d
```One-click deployment with Coolify.*Links:*
- GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;supercheck-io&#x2F;supercheck" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;supercheck-io&#x2F;supercheck</a>
- Docs: <a href="https:&#x2F;&#x2F;supercheck.io&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;supercheck.io&#x2F;docs</a>Happy to answer any questions about the architecture, design decisions, or roadmap.

Show HN: Supercheck.io – Open-Source AI-Powered Test Automation and Monitoring

Hi HN,I built Locus, an open-source project management platform designed for engineering teams that want to use AI coding agents.The core idea: plan sprints and manage tasks in a cloud dashboard, but all code execution happens locally on your infrastructure. Your source code never leaves your machine.How it works:- locus plan: AI generates a sprint plan by analyzing your codebase. It uses multi-agent roles to break down directives into structured tasks with complexity estimates and risk assessments. You can reject and iterate on plans before approving.- locus run: An agent picks up tasks from the sprint, executes them sequentially on a single branch, auto-commits after each task, and opens a PR when the sprint is done. Supports both Claude and Codex as backends.- locus review: Review that understands your full codebase, not just diffs. Detects bugs, security issues, and performance problems. Posts review comments directly to GitHub PRs.- locus discuss: Have architectural discussions with AI that has full project context. Insights and decisions are automatically extracted and saved.- Telegram bot: Manage your agent remotely from your phone.- VSCode extension: Chat with AI in your editor with full repo context.The whole system is free, self-hostable, and works with your existing GitHub workflow. There&#x27;s a one-command installation script for Ubuntu&#x2F;Debian&#x2F;macOS.Tech stack: TypeScript monorepo with NestJS API, Next.js dashboard, and a Bun-bundled CLI.I&#x27;m a solo developer building this because I was frustrated with the disconnect between planning tools and actual code execution.Would love feedback on the approach and any features you&#x27;d want to see.

Show HN: Locus – AI agents that ship your code

Transcriptum is an audio and video transcription service powered by WhisperX: speaker diarization, word-level timestamps, 50+ languages, and optional AI analysis (summaries, Q&amp;A, topics, sentiment, action items, fact-checking) via multiple LLM providers (OpenAI, Gemini, DeepSeek).You can upload files or paste a YouTube URL; we download and transcribe. Export as TXT, SRT, VTT, DOCX. Built with NestJS, Next.js, Prisma&#x2F;PostgreSQL; subscriptions are handled with Polar.I built this to have accurate, private transcription without locking into a single vendor, and to combine transcription with analysis in one place. Would love feedback from anyone who transcribes meetings, podcasts, or long-form content.

Show HN: Transcriptum – fast video transcription with speaker labels and summary

Hey HN,I built ToMusic, an iOS app that turns text descriptions into full songs (lyrics, vocals, and instrumentals) in seconds.How it works: You describe what kind of song you want (genre, mood, tempo, vocal style) or paste your own lyrics, and the app generates a complete, original song. It also works for pure instrumentals like background music, beats, and soundtracks.It supports 150+ genres (Pop, Jazz, EDM, Classical, Hip Hop, Metal...), 30+ moods, and 5 different AI models each with different strengths: longer tracks up to 8 minutes, better song structure, faster generation, etc.Tech stack: Native iOS built with Swift&#x2F;SwiftUI. Backend runs on NestJS with multiple AI music generation models, behind NGINX as a reverse proxy handling SSL via Let&#x27;s Encrypt. Built-in player with synchronized lyrics and audio visualizations. Streaming playback so you don&#x27;t have to wait for the full track to finish generating.I built this for content creators who need custom music for videos, musicians looking for quick inspiration, and honestly anyone who&#x27;s ever had a melody in their head but couldn&#x27;t produce it. No musical training needed.Would love to hear your feedback. Happy to answer questions about the AI models, the generation pipeline, or the iOS development side.

Show HN: ToMusic – Turn text prompts into original songs with AI (iOS)

Hey HN,I&#x27;m a solo dev and I built Invocrea because I was tired of spending hours every month on invoicing. Most tools out there are bloated, expensive, or just ugly.<pre><code> Invocrea lets you create and send professional invoices in under 30 seconds. The stack is Next.js + NestJS + MongoDB.

 The feature I&#x27;m most excited about: AI-generated invoice templates. You describe the style you want, and it generates a custom template for you. No more generic-looking invoices.

 What it does:
 - Create invoices&#x2F;quotes with smart auto-completion
 - Track payments (paid, pending, overdue) in real-time
 - Automatic reminders for unpaid invoices
 - Professional PDF export with your branding
 - AI-powered template generation
 - Client management with full billing history

 It&#x27;s free to start. If you want to try a paid plan, use code AVSE78 for 30% off.

 Would love your feedback on the product and the AI template generation. What would you improve?</code></pre>

Show HN: I built an invoicing SaaS with AI-generated invoice templates

I&#x27;ve built an open-source tool for managing isolated preview environments (per PR) for backend applications. Currently provisions servers on DigitalOcean.Inspired by Netlify&#x2F;Vercel&#x27;s preview links for frontend apps, I wanted something similar for backends. Frontend apps are generally stateless and simple to preview, but backend apps work with databases, Redis, message brokers, etc., which made building a framework that works for different application types quite tricky.I recently discovered Railway offers something similar, but I still wanted to build the tool I wished existed. The learning process has been incredibly rewarding.Built with Docker, Terraform, and Ansible. Supports NestJS, Laravel, Node.js, Rust, Go, PHP, and more.Docs: <a href="https:&#x2F;&#x2F;docs.prvue.dev" rel="nofollow">https:&#x2F;&#x2F;docs.prvue.dev</a>Demo videos coming soon. Open to collaborations and contributions!

Show HN: Prvue – Self-managed preview environments for back end apps

i did a similar audit and the worst offender was duplicated config and generated files across the Next.js frontend, NestJS backend, mobile wrapper and CI. make a tiny MVP baseline you can actually ship from: one Next app, one thin backend service with a single auth route, and move CI&#x2F;mobile scaffolding into a separate repo or a generator so they don&#x27;t come along to every new project. consolidate shared types and infra code into a single package, kill unneeded dev-tooling files, and change heavy codegen to on-demand scripts that run when you add a feature. build a tiny CLI that scaffolds a feature folder instead of including every possible file in the base. that cut my new-project file count from hundreds to a few dozen. fwiw i used a starter kit that had auth and payments preconfigured, Vibe Coding Starter Kit, to get a production-ready baseline without rebuilding all that infra.


  [![Backers on Open Collective](https://opencollective.com/nest/backers/badge.svg)](https://opencollective.com/nest#backer)
  [![Sponsors on Open Collective](https://opencollective.com/nest/sponsors/badge.svg)](https://opencollective.com/nest#sponsor)

## Description

Nest is a framework for building efficient, scalable [Node.js](http://nodejs.org) server-side applications. It uses modern JavaScript, is built with  [TypeScript](http://www.typescriptlang.org) preserves compatibility with pure JavaScript and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).

Under the hood, Nest makes use of [Express](https://expressjs.com/), but also, provides compatibility with a wide range of other libraries, like e.g. [Fastify](https://github.com/fastify/fastify), allowing for easy use of the myriad third-party plugins which are available.

## Installation

```js
$ npm install
```

## Getting Started

Setting up a new project is quite simple. With npm installed, you can create a new Nest project with the following commands in your OS terminal:

```js
$ npm i -g @nestjs/cli
$ nest new project-name
```

## Running the app

```js
# development
$ npm run start

# watch mode
$ npm run start:dev

# production mode
$ npm run start:prod
```

## Test

```js
# unit tests
$ npm run test

# e2e tests
$ npm run test:e2e

# test coverage
$ npm run test:cov
```

## Support

Nest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please [read more here](https://opencollective.com/nest).

## Stay in touch

- Website - [https://nestjs.com](https://nestjs.com/)
- Twitter - [@nestframework](https://twitter.com/nestframework)

... More content comming soon ...

NestJS News

News From: hn.algolia.com

NestJS Best Practices (Yet another Claude skill)

DayTradingCentral – Free Trading Journal (Next.js, NestJS, Postgres)

Show HN: Production-Ready NestJS Back End (Multi-Tenancy, Event-Driven)

Show HN: Osprey API Tester – VS Code API Testing from NestJS Controllers/DTOs

Show HN: VaultSandbox – Test your real MailGun/SES/etc. integration

Tell HN: A production-ready "Hello World" is now ~600 files

ProjectCLI: The Swiss Army Knife CLI for bootstrapping any project

Show HN: Rikta – A modular, TypeScript-first back end framework for Node.js

Show HN: Cholesterol Tracker – Built after high cholesterol diagnosis at 33

Show HN: DreamStack – Framework-agnostic Node.js foundation - 500+ tests (~10s)

Show HN: OAuth 2.0 server with AI security agents (EU sovereign alternative)

Show HN: Spine – an execution-centric backend framework for Go

Show HN: Supercheck.io – Open-Source AI-Powered Test Automation and Monitoring

Show HN: Locus – AI agents that ship your code

Show HN: Transcriptum – fast video transcription with speaker labels and summary

Show HN: ToMusic – Turn text prompts into original songs with AI (iOS)

Show HN: I built an invoicing SaaS with AI-generated invoice templates

Show HN: Prvue – Self-managed preview environments for back end apps

Show HN: Prvue – Self-managed preview environments for back end apps