nestjs-openapi3
json-schema-to-typescript
nestjs-openapi3 | json-schema-to-typescript | |
---|---|---|
1 | 7 | |
24 | 2,785 | |
- | - | |
0.0 | 7.2 | |
over 1 year ago | 11 days ago | |
TypeScript | TypeScript | |
- | MIT License |
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.
nestjs-openapi3
-
Show HN: Remult – a CRUD framework for full-stack TypeScript
So I spent a lot of time in the Nest ecosystem, and I wrote some nontrivial libraries with a little (not a lot) of uptake (and neither are actively maintained at this point, so these are here mostly for completeness):
https://github.com/eropple/nestjs-auth
https://github.com/eropple/nestjs-openapi3
I was pretty excited by NestJS when I ran into it because, well--I don't mind magic, when it's done right. I quite like Spring Boot, for example. But NestJS's magic is...incorrect, in a lot of ways. The DI container is a little bit scary, with oddly hardcoded ways to register interceptors into request scope (itself necessary because NestJS's logging facilities aren't--or weren't at the time--decorating requests with X-Request-Id or similar, so you had to register your own) and no way to then define interceptor order.
It also has a lot of really overlapping nouns; guards are interceptors but less capable (and @eropple/nestjs-auth didn't use them at all) and the "pipe" concept for validation was itself inscrutable. To make it usable, I ended up just doing everything with decorators and interceptors, all living in request scope. And once I'd gotten it going, it was pretty nice. But it also meant broad incompatibilities with much of the NestJS ecosystem.
json-schema-to-typescript
-
Gentle Introduction To Typescript Compiler API
Compile JSONSchema to TypeScript type declarations
-
Show HN: A tool to Convert JSON schemas into TypeScript classes
Nice! Lots of tricky edge cases to do this right: there’s ambiguity in the JSON Schema spec, version-to-version changes, many popular community conventions that don’t adhere to the spec, etc. Feel free to check out the tests to understand some of these: https://github.com/bcherny/json-schema-to-typescript (shameless plug — I have maintained this library for a number of years).
-
Why JSON Isn’t a Good Configuration Language (2018)
jsonnet is my go-to language for anything related to configuration, after having tried json, yaml, TS, edn, and tasting dhall and toml. It addresses all problems in the article and more.
the composition strikes a good balance between extensiveness and ease of use.
the generated json leads to easy and portable data, and if you write jsonschemas from jsonnet, tools like json-schema-to-typescript [1] make it easy to import a consistent interface, and almost every language has a reasonably up-to-date validation library.
[1] https://github.com/bcherny/json-schema-to-typescript
-
Show HN: Remult – a CRUD framework for full-stack TypeScript
Take a look at https://github.com/bcherny/json-schema-to-typescript, too. I used it successfully at a previous job. IIRC, I had to write some code to convert OpenAPI to JSON Schema but it wasn’t onerous
-
TRPC: End-to-end typesafe APIs made easy
If you're using OpenAPI, you could use this to generate TypeScript interfaces:
https://github.com/bcherny/json-schema-to-typescript
It works really well
-
Running Out of Heap Memory While Converting JSON Schemas - Not Understanding Heap Memory/Async/Await/Promises
I'm messing around with a process to convert JSON schemas to TypeScript interfaces using json-schema-to-typescript. I have a little under 900 JSON files each containing a schema, totaling about 3.5 MB.
-
I created a tool which automatically generates typescript definitions for API endpoints
json-schema-to-typescript
What are some alternatives?
openapi-typescript - Generate TypeScript types from OpenAPI 3 specs
MikroORM - TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, MS SQL Server, PostgreSQL and SQLite/libSQL databases.
remult - Full-stack CRUD, simplified, with SSOT TypeScript entities
trpc - 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
nestjs-auth - Comprehensive handling of authentication and authorization for NestJS.
json-schema-to-ts - Infer TS types from JSON schemas 📝
graphql-zeus - GraphQL client and GraphQL code generator with GraphQL autocomplete library generation ⚡⚡⚡ for browser,nodejs and react native ( apollo compatible )
graphql - GraphQL (TypeScript) module for Nest framework (node.js) 🍷
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB