nestjs-spelunker
ogma
| nestjs-spelunker | ogma | |
|---|---|---|
| 1 | 4 | |
| 287 | 281 | |
| - | - | |
| 6.9 | 8.3 | |
| 7 months 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.
nestjs-spelunker
-
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.
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?
ogma
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
nestjs-commander - A module for using NestJS to build up CLI applications
semver - Nx plugin to automate semantic versioning and CHANGELOG generation.
loopback4-example-websocket - WebSocket example for LoopBack 4
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!
typeorm - TypeORM module for Nest framework (node.js) 🍇
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
nest-samples - A repository to hold a bunch of Nest samples, cause I'm tired of remaking them and losing them. Now it's just a sinlge repo to hold them all
nx - Smart Monorepos · Fast CI
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: