Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
I built a framework for building products for startup, just open sourced this week: https://hyperstackjs.io
e.g. there's no reason in one of these systems where you couldn't just use Axios (or fetch) on its own to make outside requests. But instead, for no good reason, Nest wants to wrap Axios for you in a way that allows you to only really grab a single instance at a time. Which is not how Axios is meant to be used. This makes it so that you can't use the baseURL config option which is one of the most important options when constructing a client that's meant to work with a particular service. You could use a named injector but at this point there's no reason to not just pass around an instance other than Nest seemingly having this alternate pointless way of doing things. So basically, yes, in this case Nest pushes you into a pattern but that pattern isn't just ugly... it's inherently limiting to you while being more verbose and decreasing readability.
I've found you can move very fast with NestJS and NestJSX CRUD, which gives you all CRUD operations out of the box, just be careful to lock it down as much as possible https://github.com/nestjsx/crud
Related posts
- Unlocking the Power of GraphQL for Beginners: A Step-by-Step Guide to Integrating GraphQL into Your Existing Project
- Api Docs v2.0-beta prototype for NestJS 😻 🚀
- Implement field permissions with FieldMiddleware
- 5 steps to create a bare minimum NestJS app from scratch!
- NestJS vs. Ditsmod: DI features for interceptors, guards, pipes and filters