papr VS Superstruct

Have you heard about Papr before? https://github.com/plexinc/papr

I also think the typescript support for mongoose leaves much to be desired. A few months ago, papr catched my eye, which looked like it was created from the lack of typesafe ORMs/ODMs for mongoDB.

You should consider either avoiding ODM as suggested by Mongodb here: https://www.mongodb.com/developer/article/mongoose-versus-nodejs-driver/ or may like to consider a lightweight one that plays nicely with mongodb native scheme validation such as Papr https://github.com/plexinc/papr. In a performant mongo db scheme design, relation between collections should not be norm and can be handled directly without using mongoose. For relations, mongoose may generate inefficient queries (more like n+1. That being said, if you must use one then mongoose is indeed more widely used and mature.

You can check out Superstruct documentation here.

This is where I saw compiled folder has superstruct’s minified code.

However, working with the unknown type is less convenient than merely specifying the desired data type. Apart from type-casting, there are multiple ways to convert the unknown type into the required data type. One such method is utilizing the Superstruct library to validate data at runtime and throw detailed errors if the data is invalid.

For example, the superstruct library is a lighter alternative to Zod. This library is more suitable for use on the client side since it has a relatively small size (13.1 kB vs 3.4 kB).

Banditstash, like all the newer validation libraries (yup, zod, superstruct, typed) can auto-generate TS type from a JS schema:

Superstruct 1.0.3

Inside the action, the first thing we're going to do is get the formData using the request object. Then we will create an object from the formData data that will later be validated by our superstruct schema.

You could use Zod or Superstruct to validate the types of values, or use typestack/class-validator if it makes sense.