typescript-starter VS nestjs-typegoose

Let's say you want to create a new NestJS standard application from scratch but taking the full control of your dependencies, scripts and source code. Thus, you don't want to use the usual npx @nestjs/cli new command (which basically bootstraps the typescript starter project) since you wish a bare minimum app.

You don't need to use the Nest CLI if you don't want to. You can literally just create a index.ts file, use NestJS within it and run it with ts-node index.ts (though you gotta make sure you have the correct tsconfig.json)

Another option is to clone the starter repo from GitHub. Note that to install the JavaScript flavor of the starter project, we can clone this repo, but you’ll need Babel to compile vanilla JavaScript).

git clone https://github.com/nestjs/typescript-starter.git project cd project yarn yarn add -D prisma npx prisma init

As much as I don't like to use it, there are people who decide that NoSQL and MongoDB are the way to go for their application. Before v7, Nest didn't provide it's own decorators for a mongoose integration, and developers had to use the standard schema approach. While there's nothing wrong with this, it definitely does bring in some pain points when it comes to types and DTOs, so a SchemaFactory was created to allow developers to keep using classes to define their mongoose schemas. This works pretty well, but does admittedly lack some features, like virtuals and static methods. These can be added to the generated schema, but Typescript will not know about them. I usually suggest people use nestjs-typegoose instead of Mongoose/Typegoose integration with NestJS.