wtfjs VS typegoose

Me in the interview: "Generally, no, a variable can only be assigned one numeric value at a time. However, Javascript is famous for unpredictable behaviors in variable comparison statements, for instance [] == ![]. There's actually a whole library built around documenting this type of behavior this for comedic value, and other more serious libraries geared towards solving the problem. So it's possible that some obscure variable assignment scenario would result in that line evaluating as true, but it's not something you'd expect to encounter in the real world. This has gotten a lot better with typescript and es2022, but still something you need to watch for a bit."

I do see that point of view, didn't think of that, there are some aspects of go which are a bit weird if you never touched lower abstraction languages, yet once you learn what they are, you are all set and you can code in anything. go has the least amount of gotchas I have seen in any programming language. compare it with loads of the weird stuff javascript does https://github.com/denysdovhan/wtfjs and go is like heavenly lol

Its a very poorly designed language. Its syntax and semantics are often confusing and unpredictable. There is no well defined mental model of how constructs work in this language.

WTF JS

😎 A great guide to Javascript that is both simple and wonderful, but also difficult and fun that seems like bullshit. -> wtfjs

So we started researching the state-of-the-art and discovered several libraries that could fit our requirements. The best candidates we were able to find were Mongoose, Typegoose, and TypeORM. Mongoose is a well-known Node.js library for MongoDB that implements the Data Mapper pattern and lets developers define schemas to constraint the data models associated with their domain objects. However, Mongoose works with concrete data models, which in a complex domain model scenario results in query logic duplication. Typegoose is a type-safe Mongoose wrapper that allows schema constraint declaration at domain object field level via JS decorators. Unfortunately, those very decorators leak persistence logic into the domain model. Besides, Typegoose also implements the Data Mapper pattern, thus sharing the same drawbacks of Mongoose. TypeORM, on another hand, implements the Repository pattern and provides some basic support for MongoDB. However, TypeORM presents several limitations compared to Mongoose.

This is where Typegoose comes in, which is basically a wrapper to create TypeScript templates in an easy way. I bet that at some point you've already tried TypeORM and most likely liked working with classes and decorators to define the fields of your entities.

There's so many more cool features and utilities with typegoose, such as creating static and instance methods directly inside of the class, that I would advise you to check out at the official docs!

Sry for asking, can't you use https://github.com/typegoose/typegoose for all of the typing?

I found this: https://github.com/typegoose/typegoose but I feel like the API is not very readable.

If your library is written in TypeScript, you can automatically generate both JavaScript code (to support all users) and TypeScript declaration files (which add TypeScript types to JavaScript code). You will almost never need to export TypeScript files in your package, unless all of your users will use TypeScript (i.e. for something like typegoose).