routing-controllers
openapi-typescript
Our great sponsors
routing-controllers | openapi-typescript | |
---|---|---|
6 | 16 | |
4,330 | 4,556 | |
0.6% | - | |
9.0 | 9.3 | |
5 days ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
routing-controllers
-
Node.js 20 is now available
The standard is express. I say that with some glibness, but its the only true answer: a ton of the other higher level frameworks and pluggable middlewares still rely on the core express Request/Response types. And there are a ton of higher level frameworks, if the number of distinct replies wasn't obvious.
I really like express + routing-controllers [1], if you're on typescript.
[1] https://github.com/typestack/routing-controllers
-
Do you use Swagger/OpenAPI to document your APIs? If so, what is your preferred way to generate the docs?
I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc
- How to implement Socket.io using Typescript
-
Creating a web server with typescript, should I go for express or fastify? Which one has better packages for typescript integration? Any recommendations for packages for each?
If I don’t want to use nest then I would use express or koa with routing-controllers. Using this package you can write controllers with classes and decorators which is similar to nest js. There are a lot of other features too.
- Maintaining REST API Documentation with Node.js
- Great examples of idiomatic (backend) TS code
openapi-typescript
-
Writing type safe API clients in TypeScript
OpenAPI TypeScript
-
Django 5.0 Is Released
I'll preface all of this with a couple esoteric design goals that I had in mind:
1. I actually _want_ an SPA. You might not need an SPA, if you don't need one then Vue/React/etc are overkill, etc.
2. I want to power as much of the SPA as I can using the same REST API as my core product, both for dogfooding reasons and for consolidation. Many people might argue that this is a bad idea.
---
With that in mind, some specific packages that I highly recommend:
1. Django-vite (https://github.com/MrBin99/django-vite). This makes it very easy to serve an SPA from the actual django response/request model
2. Some sort of way to get type information (if you're using TypeScript) into the frontend. I use a frankensteined system of the OpenAPI spec that django-ninja generates + openapi-typescript (https://github.com/drwpow/openapi-typescript). This means when I add, say, a new field to a response in Django, I immediately get typechecking for it in Vue — which has been _tremendously_ useful.
3. Django-typescript-routes (a package I extracted and open-sourced!: https://github.com/buttondown-email/django-typescript-routes) which gives your front-end routing information based on the Django router.
- OpenAPI-TypeScript – OpenAPI schemas in TypeScript
-
Tell HN: Postman just wiped all my stuff
Glad to see alternatives but disappointed that Bruno does not support OpenAPI specification.
At my company, we hand-edit OpenAPI specs in YAML and it gets consumed by many tools that generate types[0], static analysis and dynamic checks[1]. The OpenAPI spec itself is linted[2]. And of course, Postman consumes OpenAPI.
Tools that are built on open standards will naturally see greater adoption over those that use proprietary formats.
[0]: https://openapi-ts.pages.dev
-
tRPC – Move Fast and Break Nothing. End-to-end typesafe APIs made easy
Another great library to generate TS types from OpenAPI is https://github.com/drwpow/openapi-typescript . It provides the types as single objects you access via indexing, which is pretty nice. There's a partner library to generate a typed fetch client.
-
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?
-
Should I add Redux?
REST
-
Building a Secure Database-Centric OpenAPI in 15 Minutes
In this sample, we'll achive it using openapi-typescript and openapi-typescript-fetch.
- GRPC Gateway API Client?
-
Need help to generate openapi services for vue
I've used this, and it works very well. https://github.com/drwpow/openapi-typescript
What are some alternatives?
tsoa - Build OpenAPI-compliant REST APIs using TypeScript and Node
remult - Full-stack CRUD, simplified, with SSOT TypeScript entities
nestjs-commander - A module for using NestJS to build up CLI applications
zod - TypeScript-first schema validation with static type inference
fastify-openapi-glue - A plugin for the Fastify webserver to autogenerate a Fastify configuration based on a OpenApi(v2/v3) specification.
proposal-decorators - Decorators for ES6 classes
websocket-typescript
nestjs-openapi3 - OpenAPI 3.x document generation and serving for NestJS.
swagger-jsdoc - Generates swagger/openapi specification based on jsDoc comments and YAML files.
nestjs-auth - Comprehensive handling of authentication and authorization for NestJS.
routing-controllers - Create structured, declarative and beautifully organized class-based controllers with heavy decorators usage in Express / Koa using TypeScript and Routing Controllers Framework. [Moved to: https://github.com/typestack/routing-controllers]
openapi-comment-parser - ⚓️ JSDoc Comments for the OpenAPI Specification