awesome-nestjs VS Nest

check this repo you might find something there => https://github.com/nestjs/awesome-nestjs

I worked full stack with .net and angular for a year. I would say that is you think too OOP, you might try to do things that typescript doesn't do well. Like extending one class with multiple base clases. I've been working with Nestjs for one year or so in a personal project and I think it's amazing. You can do simple things like MVC and rest apis with little efforts. You can also work with more complex patterns like DDD and event sourcing pretty much out of the box. Because it is also JavaScript and node you can use a plethora of packages that solve your problems similarly as .net like Automapper, typeorm/mikroorm (entity framework like). In addition to a ton of open source projects that are using nestjs. Check https://github.com/nestjs/awesome-nestjs so you can explore how to get started. I would recommend you to use NX.dev to work your mono repo, it is super powerful and easy to maintain a full node mono repo. And it even has a plug in to add c# .net core projects as well https://github.com/nx-dotnet/nx-dotnet. So you can still leverage on the same tech you already know for more complex things like Identity server.

You can find here

Possibly one of the boilerplates on awesome-nestjs?

I use Nest.js for backend development, here's a repository with many resources regarding nest, it also includes list of real world projects using Nest.js.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/