@thisismissem @adonisframework Yes, I saw it, but it sadly uses uses also old style decorators from TS with `emitDecoratorMetadata: true`.
My implementation does not use `emitDecoratorMetadata: true`!
I also orientate myself currently a bit between #nestjs, #quarkus and #springboot.
Discover the silent security risk lurking in your NestJS applications. https://hackernoon.com/bad-validation-is-breeding-security-nightmares-in-nestjs #nestjs
pivoting from #ZenStack towards just using #NestJS/#prisma “manual” solutions to build a #REST #API.
would still like to have some way to quickly serialize our prisma models into a format like JSON:API (or HAL). but when I look at https://jsonapi.org/implementations/#server-libraries-node-js (and with some additional searching):
there are numerous full frameworks and a few serializers but most of them have not been touched in years. is the Javascript world still stuck in #graphQL land? or am I just not looking in the right places?
I was leaning to adopting #ZenStack to build out our #REST #API on top of #NestJS and #Prisma
https://zenstack.dev/docs/the-complete-guide/part3
But now I am having 2nd thoughts, since in v3 ZenStack is dropping Prisma in favor of a (for now at least) API compatible alternative. We have standardized on Prisma so this would put is on a path to have to debate this topic (again).
https://news.ycombinator.com/item?id=44328662
Any thoughts on this?
looking for an #OSS #APIgateway
* API keys (API users) + Oauth (website) for auth
* rate limiting + protection against content crawling
* queuing requests to prevent overloading our self-hosted AI models
* ability to track usage so that we can charge expensive API calls to users/orgs
* basic monitoring
API will most likely be written in #NestJS, another likely using #FastAPI (or something else in #Python). I like #GitOps. Doesn’t need to handle insane traffic just make the above things easier.
Day 7
24 test suites, 153 tests passing.
Solid coverage across service and controller layers in my modular monorepo. Strict typing (TypeScript), full DTO validation, and realistic mocks across complex relations (TypeORM).
Next: fine-tuning error handling & exploring e2e strategies.
https://write.as/bmariusz/24-test-suites-153-tests-passing-scaling-confidence-with-every-assertion
Day 6
TL;DR: Groups, memberships, hierarchy — all dynamic now.
Released backend v0.3.0 
Users can belong to multiple groups with typed roles Groups can form hierarchical or overlapping structures Roles are normalized via reference types
Built with NestJS + TypeORM. Documented via Swagger.
https://write.as/bmariusz/building-a-flexible-group-structure-with-nestjs-and-typeorm
Day 5
TL;DR: Continued work on backend security — role-based access is now fully wired up.
Got fine-grained role-based access control fully working today.
• Roles loaded from PostgreSQL
• Injected into JWT during login
• Validated via custom `@Roles()` + `RolesGuard`
• Authenticated via `@UseGuards(JwtAuthGuard)` globally
• Introduced `@Public()` decorator to bypass guards for public endpoints
• Swagger supports Bearer token for testing
Took a while to get the role propagation into the token right — the key was enriching the `validateUser()` result, not just fetching data from DB.
Modular, clean, and no magic. Feels good. 
more on: https://write.as/bmariusz/continuation-securing-routes-with-jwt-and-role-based-access-control
#CloudNative #TypeScript #NestJS #Nextjs #InsuranceTech #Microservices #monorepo
#codingdays #swagger #jwt #jwt_auth #programming
Day 4
TL;DR: Full Swagger docs + JWT auth with registration and login are live.
Today’s work focused on two key improvements.
1. Swagger documentation was extended across all API layers. DTOs, entities, and controllers were enriched with `@ApiTags`, `@ApiOperation`, `@ApiResponse`, and detailed `@ApiBody` annotations — including real-life examples for request bodies.
2. JWT-based authentication was implemented. A secure registration flow was added, with password hashing via bcrypt. A login endpoint now issues access tokens containing user ID, email, and roles. All logic is encapsulated using Passport strategies (local and JWT). The next step will be protecting routes with guards and role-based access.
#CloudNative #TypeScript #NestJS #Nextjs #InsuranceTech #Microservices #monorepo
#codingdays #swagger #jwt #jwt_auth #programming
Day 0:
TL;DR: Set up the basic foundations for a new system: database schema finalized, core backend modules scaffolded, and initial API contracts defined. The real work begins now.
No hype. Just building.
Today I worked on building the core backend infrastructure for a cloud-native insurance platform. Key points:
Modular microservices architecture based on NestJS
PostgreSQL schemas designed for flexibility — no hardcoded values, all dynamic
Using TypeScript with ESM modules for better code organization
Setting up communication patterns between backend and Next.js frontend
Focus on scalability and simplicity in cloud deployment
This lays a solid foundation for a system built from scratch to replace legacy solutions and support future growth.
#CloudNative #TypeScript #NestJS #Nextjs #InsuranceTech #Microservices
#codingdays #programming
Immich is primarily written in TypeScript and JavaScript, with a significant amount of code also in Dart and Svelte. The Immich Server itself is built using TypeScript and Node.js, and leverages the Nest.js framework, Express server, and Kysely. The GitHub repository indicates that TypeScript accounts for 48.8% of the code, Dart for 28.7%, Svelte for 17.8%, and other languages contribute the remaining percentage.
【即試せる！】Webでビデオ通話してみたくない？Nest.js × WebRTCで作ってみた
https://qiita.com/rtkjm22/items/ee08228f170c9e6e81a3?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
あなたはすぐに解決できる？NestJsのコントローラ実装で2時間詰まった話
https://qiita.com/Nao52/items/55ac0b56ecba483c52c8?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
I despise `it.each(testCases)` ….
Feel it’s like debugging a pile of mud…
Exploring LLM-powered code migration! 
Check out https://www.linkedin.com/pulse/code-migration-using-llms-glenn-engstrand-c7ixc/ which dives into my experience migrating a Java Spring Boot microservice to TypeScript Nest.js using Llama 3.3 and GitHub Copilot. I share valuable insights on the benefits and challenges of LLM-assisted development, highlighting the productivity gains and the need for manual refinement. #LLM #CodeMigration #TypeScript #NestJS #DeveloperProductivity #GitHubCopilot
Today I thought I would use gRPC instead of 
Graphql in a project. Now I will need to change a lot of code, but a highly loaded service is expected in the future, so this is good for the whole project. Maybe someone can suggest something?
Qiita - 人気の記事 
