CUA VS Nest

Bias: I maintain a fullstack universal app template called CUA that uses Expo/Nextjs/tRPC/Solito/Tamagui.

Most of it is, but there are still parts that arent smooth integrated, such as navigation and authentication, and others that may need separate implementations due to not having a ready-made wrapper. create-universal-app and create-t3-turbo are good starting points.

I'd likely go for a mobile first approach and start with:

create-universal-app : https://github.com/chen-rn/CUA

Which would give me:

Yes, try either:

The official «Tamagui + Solito + Next + Expo Monorepo» starter:

https://github.com/tamagui/tamagui/tree/master/starters/next...

Or the more recent version that builds on that and adds tRPC and authentication (with Clerk):

create-universal-app - https://github.com/chen-rn/CUA

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/