typescript-starter VS nestjs-typegoose

Find a project starter like this one.

Hi, This is a template for kickstarting a TypeScript project a bit like TSDX or typescript-starter but its specificity is that it isn't a CLI tool. All the automation happens in the GitHub action workflow. It's really focused toward managing the life cycle of a NPM module. It publish on NPM on your behalf when you update the package.json version, it let you publish release candidate, ect... I encourage you to click on "Use this template" and see for yourself :)

Hi :) - I'm starting up a new Typescript library using typescript-starter, by bitjson. It comes with a bunch of goodies right out of the bag (some admittedly new to me), and makes for a very thorough development experience.

Btw I edited my previous reply with another tip that might help. Also here’s the TS starter tool I like to use. I forked / customized it but the initial version is really easy to use.

View on GitHub

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.