ts-rest
ogma
| ts-rest | ogma | |
|---|---|---|
| 3 | 4 | |
| 1,976 | 281 | |
| 4.3% | - | |
| 9.3 | 8.3 | |
| 7 days ago | about 2 months 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.
ts-rest
- ts-rest 🧙♂️E2E type safety, no code-gen, supports all your favourite frameworks, tiny bundle size and incrementally adoptable! Just hit 250 ⭐️
-
Nestjs + pnpm monorepo
Yup! Exactly what I’m doing with https://github.com/ts-rest/ts-rest
- tREST, a lib to make E2E APIs easy to make for Nest.js or Express backends, fully type safe, HTTP errors fully handled, with optional react-query, Zod and OpenAPI support
ogma
-
Overriding [Nest] prefix
Why not use a dedicated logging library, like ogma or pino?
-
Nestjs + pnpm monorepo
To echo the other's here, Nx has been an amazing dev experience for me! I use it for ogma, for nest-commander, testing-nestjs, and for nest-samples and @nest-lab/, all using pnpm as a package manager.
-
Node.js frameworks
This absolutely isn't true. I'm both on the core team and a maintainer of several open source modules for Nest (nest-commander for CLI creation, ogma my own logger that has a really powerful interceptor, nestjs-spelunker which can print out an object representation of your Nest application and help with module debugging for dependency resolution, and a few more). The command module is even featured in the docs.
-
Automating your package deployment in an Nx Monorepo with Changeset
Overall, I'm pretty excited to have this flow automated and working through three of my favorite package management tools. Everything will also work if you're using a yarn workspace instead, just change the sed script to modify the workspace file for yarn instead of the one for pnpm. I'm currently using this for my ogma and nest-commander repositories, feel free to have a look if you need some inspiration and/or real life examples. If you're developing packages and using an Nx workspace and need automated package deployment, give this a shot.
What are some alternatives?
aoe2-data-api - Fan made data api for Age of Empires II game
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
react-query-kit - 🕊️ A toolkit for ReactQuery that make ReactQuery hooks reusable and typesafe
semver - Nx plugin to automate semantic versioning and CHANGELOG generation.
power-search - Search several services in one interface.
nestjs-commander - A module for using NestJS to build up CLI applications
nest-lab - A repository to hold "experimental" packages for Nest. Honestly, I'm just tired of not having a good scope to put packages under :smile_cat:
testing-nestjs - A repository to show off to the community methods of testing NestJS including Unit Tests, Integration Tests, E2E Tests, pipes, filters, interceptors, GraphQL, Mongo, TypeORM, and more!
infinite-scroll - Creating an infinite scroll with react js ♾️
typeorm - TypeORM module for Nest framework (node.js) 🍇
clover - Server routes augmented with Zod and OpenAPI
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀