Alternatives
Products that do what I made a fetch client builder to make API calls simpler and safer does
I built this library because I kept rewriting the same fetch wrapper for every project. Each time, I needed the same core features: - Make fetch throw errors to integrate smoothly with libraries like TanStack Query - Add sensible defaults to the Fetch API, like a base URL and authentication headers - Validate responses for type safety when OpenAPI isn’t an option I also wanted the library to feel exactly like using fetch — no new API to learn, and no extra friction for my teammates. While there are other great options out there, I found many were either too rigid or too bulky. Doesn’t it…
- 1
- 2
Instantly generate openapi (OAS) 3.0.0 REST + GraphQL APIs
2019
- 3IA
Hey there HN! I just wrapped up an all-day documentation spree for Instant API, a JavaScript framework for easily building web APIs that implements type safety at the HTTP interface. It uses a function-as-a-service approach combined with a slightly modified JSDoc spec to automatically enforce parameter and schema validation before HTTP requests make it through to your code. You just write comments above your endpoint functions and voila, enforced type safety contracts between your API endpoints and your developers. OpenAPI specifications are generated automatically as a byproduct of simply…
2023 · github.com
- 4
- 5
- 6FR
2023 · github.com
- 7AF
2020 · github.com
- 8WV
2017 · wrapapi.com
- 9NW
2021 · github.com
- 10
- 11
- 12FB
2019 · fastapi.tiangolo.com
- 13TA
2023 · typeapi.org
- 14AJ
I've been building a web UI library for a side project of mine. I thought it might be useful to others, so I'm releasing it as open source. To put it simply, I realized that most of my pain points with React come from its declarative model ui=f(state). So I'm trying something that I'm calling "imperative JSX." Instead of treating JSX as the source of truth for your UI, it essentially becomes a query interface for DOM manipulation. I first had the idea for it a few months ago, and only began writing it in earnest last week, so it's extremely early and nowhere near production-ready. Still, I'd…
2024 · npmjs.com
- 15TO
Hi HN! We’re excited to share our new code generator that lets you ship high-quality TypeScript SDKs, that your users will love, from your OpenAPI documents. Our ongoing goal is to help you build one SDK that runs anywhere modern JavaScript runs. This includes new runtimes like Deno and Bun in addition to the ever-popular Node.js. Additionally, the popularity of AI has meant server-sent events and file streaming are also commonplace - we wanted to cover these use cases too. This explosion in new runtimes and ways of interacting with APIs shifts cognitive burden on API developers often having…
2024 · speakeasyapi.dev
- 16AT
This began as a passion project and an opportunity to learn new tech. I've always experienced frustration developing APIs, especially the RESTful CRUD style of data APIs. It always felt like I was repeating the same patterns over and over again, and that was tedium I didn't want. A little over a year ago, I wanted to learn more about Go, Firecracker microVM, and Svelte and thought "Could I build an API framework that was just a simple description of resources? What would that look like?" That lead me to https://firecracker-microvm.github.io/, which landed me on…
Dec 2025 · attainable.dev
- 17IB
Hey everyone! Some time ago I was analyzing why React apps are so hard to optimize, and came to a conclusion that the lack of atomic updates is the culprit. I made an experimental library which basically updates everything in place directly in HTML. At some point I became aware that Solidjs exists, which is a very similar idea, but at the end of the day I realized my approach to API is quite different and warrants the existence of my library (my state primitive allows selector subscriptions, array iterators return a state primitive with the element, allowing to never re-render the whole…
2024 · github.com
- 18SQ
TL;DR- Libninja will generate world-class client libraries for you, without you needing to fiddle with openapi-generator, maintain build pipelines, and so forth. If you just want Rust, reach out, and I'll create your client library at no cost, because I want to help Rust's ecosystem grow. -- Hi HN, I got into Rust in a big way about 9 months ago. While the language is quickly maturing, one large gap in the ecosystem is immature or non-existent client libraries for common API services like Plaid, Stripe, Twilio, Github, Slack, and so on. The existing openapi-generator templates create Rust…
2022 · libninja.com
- 19OS
We built an open-source tool that scans your codebase and generates OpenAPI docs in minutes. Right now it supports Rails, Go, Python, and NodeJS frameworks, and we will keep adding more. It picks up routes, params, request bodies, and models directly from the code and outputs a clean OpenAPI spec you can drop into your workflow.
Nov 2025 · github.com
- 20BP
Hi all, I'm one of the authors of Serverless-Stack.com — an open source guide to building full-stack apps with AWS Lambda and React. Since it's launch in 2017, it's become one of the most widely read guides for building Serverless apps. Today we are adding a new section to the guide that walks you through the best practices of building large Serverless applications. It tries to address some of the most common questions that teams have: - How should my project be structured when I have dozens of interdependent services? - How should I manage my environments? - What are the best practice for…
2019
- 21CA
A couple years ago I was really frustrated by Postman, it couldn't do basic JSON schema validation, and didn't interoperate well with the OpenAPI spec I had to use for serverless deployments. On top of that, they started requiring an account and cloud sync, and other things I just wasn't comfortable with. So what's an engineer to do? Build yet another API Client of course! [0] It's still fairly rough and crashes more often than I like, but it's basically at the point that I've switched most of my usage so I figured I would rip off the bandaid and do a Show HN. Short list of some of the…
2024 · callosum.dev
- 22AH
Hi! My name is David and I wanted to show you a react (and solidjs) library I've built over the last months. The intention behind it is, that there are some actually useful use cases for AI on the frontend that are largely unexploited still. LLMs are particularly good at extracting structured information from unstructured text and thats really useful for any types of forms - which can be multimodal. Setting up server side logic for AI usage can take time. Streaming data to the frontend and parsing it there to make it usable can be frustrating. Imho thats one of the reasons why people…
2025 · ai-hooks.dev
- 23OS
2016 · github.com
- 24OI
2017 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →