fastify-swagger VS axios

With Speakeasy, you can create client SDKs based on an OpenAPI specification. Fastify ships with the @fastify/swagger plugin, which provides convenient shortcuts for generating good OpenAPI specifications. We'll start this tutorial by registering @fastify/swagger in a Fastify project to generate a spec.

First let’s get our current OpenAPI specification out of Fastify and onto the file system. If you have not added the https://github.com/fastify/fastify-swagger plugin first go do that. Then use this simple script I called generate-spec.ts to write your OpenAPI specification to the filesystem.

The fastify-swagger docs has an example https://github.com/fastify/fastify-swagger

@fastify/swagger is a fastify plugin to serve a Swagger UI, using Swagger (OpenAPI v2) or OpenAPI v3 schemas automatically generated from your route schemas, or from an existing Swagger/OpenAPI schema.

On the Node.js framework side of things, Fastify has support for Swagger with the fastify-swagger plugin.

With this approach, backend can be any programming languages that support OpenAPI or Swagger. Personally, I use fastify-swagger; but I can also be things like Python's FastAPI or Golang's Gin/Buffalo/Native.

For example, when using the HttpModule module from @nestjs/axios we can use the dynamic module HttpModule.register() to configure our Axios instance. That module exposes a HttpService that has such configuration. But what if we want to have many Axios instances, each one with its own config and import everything in one module?

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.

NestJs HttpModule