papr
typebox
Our great sponsors
papr | typebox | |
---|---|---|
4 | 57 | |
418 | 4,227 | |
3.3% | - | |
9.4 | 8.8 | |
3 days ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
papr
- Making the World (Type) Safe for MongoDB Queries: Papr v11
-
We're building Bridge-Mongo: a fully typed MongoDB ORM, built on top of Mongoose.
Have you heard about Papr before? https://github.com/plexinc/papr
-
Why is mongoose typed so loosely?
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.
-
typeorm or mongoose?
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.
typebox
-
Popular Libraries For Building Type-safe Web Application APIs
The documentation can be found here.
-
I write HTTP services in Go after 13 years (Mat Ryer, 2024)
So far I like the commonly used approach in the Typescript community best:
1. Create your Schema using https://zod.dev or https://github.com/sinclairzx81/typebox
2. Generate your Types from the schema. It's very simple to create partial or composite types, e.g. UpdateModel, InsertModels, Arrays of them, etc.
3. Most modern Frameworks have first class support for validation, like is a great example Fastify (with typebox). Just reuse your schema definition.
That is very easy, obvious and effective.
- Where DRY Applies
-
Has anybody used Typia library?
There's a ton of schema validators out there and most devs have their personal favorite. Mine was zod and is now typebox + ajv.
- I'm looking to use my openapi spec to dyanamically create types
-
How can I generate typescript types?
If you're willing to document your API with an OpenAPI schema, then it should be possible to generate TypeScript types based on the OpenAPI schema with something like openapi-typescript. Also, Typebox can generate JSON schemas, maybe it can be used to generate something that the front-end can also use?
-
[AskTS] What do you think will be the future of runtime type checking?
Well, I do provide extensibility for those bullet points you've listed to varying degrees (both schema and type representation), as well as offering a reference implementation for expressing a entirely different schema specification under the type system (specifically RFC8927 / JSON Type Definition). Reference implementation here. As for JSDoc, It's supported in code hints.
- TypeBox: Runtime Type System Built on Industry Standards
- TypeBox: A Type System for JavaScript built on Industry Standard Specifications
-
Building a modern gRPC-powered microservice using Node.js, Typescript, and Connect
In setting out to build this service, we wanted to use gRPC for its APIs. We’ve been reaching for REST when building APIs so far, primarily out of necessity, i.e., our public APIs needed auto-generated client SDKs and docs for developers working with them. We built those APIs with Fastify and Typebox but felt burned by a code-first approach to generating an OpenAPI spec. I’ll spare you the details and save that experience/learning for another article. Suffice it to say we love gRPC’s schema-first approach. This blog post summarizes our feelings well
What are some alternatives?
Mongoose - MongoDB object modeling designed to work in an asynchronous environment.
zod - TypeScript-first schema validation with static type inference
json-schema-to-ts - Infer TS types from JSON schemas 📝
zod-to-json-schema - Converts Zod schemas to Json schemas
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
ajv - The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)
Superstruct - A simple and composable way to validate data in JavaScript (and TypeScript).
class-validator - Decorator-based property validation for classes.
quicktype - Generate types and converters from JSON, Schema, and GraphQL
openapi-typescript-validator - Generate typescript with ajv validation based on openapi schemas
vite - Next generation frontend tooling. It's fast!
ts-json-schema-generator - Generate JSON schema from your Typescript sources