Alternatives
Products that do what Samen – build API's with TypeScript, get a typesafe client SDK for free does
- 1
- 2
- 3
- 4
- 5KB
2020 · kretes.dev
- 6
- 7
- 8ST
2016 · github.com
- 9CR
2018 · github.com
- 10TO
2014 · tyk.io
- 11AT
2019 · blog.hediet.de
- 12KF
I built KubernetesJS because I was frustrated with the state of Kubernetes tooling for TypeScript developers. Most existing clients, like kubernetes-client, were last updated five years ago and rely on generating clients at runtime from Swagger specs. That approach works, but it lacks strong typing, good auto-complete, and tends to feel brittle in larger projects. KubernetesJS also uses the Kubernetes Swagger schema, but instead of generating clients at runtime, it generates fully-typed static TypeScript code at build time. That means you get excellent TypeScript support, predictable APIs,…
2025 · github.com
- 13
- 14TO
Jul 2026 · tinbase.dev
- 15FT
Hi HN, I’ve been building 'Fragno', a toolkit for building full-stack TypeScript libraries that work seamlessly across frameworks like Next.js and SvelteKit. Traditional libraries are built to integrate on either the frontend or backend. Glue code ends up being re-implemented for every project: API routes, documentation (OpenAPI), client-side integration, etc. With Fragno, you can write libraries that include API routes and client-side hooks/logic. Users can integrate a Fragno library into their application with just a couple of lines of code. This embeds the API routes and lets them…
Oct 2025 · fragno.dev
- 16TS
2024 · litdb.dev
- 17D1
2015 · blog.duoco.de
- 18TS
Hi HN, I’m Guillaume, the cofounder of Bearer, an Open Source SAST solution. After launching a few weeks ago here on Hacker News with support for Ruby and JavaScript stacks, I’m happy to report we’ve just released a new version (v1.2) with TypeScript support! In terms of code coverage, we use the same rules already implemented for vanilla JavaScript, but as usual, you can build your own. The rules list is here: https://docs.bearer.com/reference/rules/ It’s a first version for TS, but we believe that thanks to the pre-existing JavaScript support it should already…
2023
- 19SR
2022 · github.com
- 20IM
Jul 2026 · github.com
- 21II
I was building my personal agent, but I had to use Telegram, as it was the easiest platform to integrate. I wanted to build the harness and agent, not the infrastructure around these two, yet my UX was struggling. I stick to iMessage, and then I had to use another app to interact with my agent... So I spent a weekend on building a TypeScript SDK, that unifies how to interact with different iMessage providers (as there is no official way to use iMessage), so you can play around with them, without having to commit to one, nor with a need to rewrite half of the codebase to change the…
Jul 2026 · github.com
- 22AA
2020 · arc.patico.pro
- 23IM
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…
2025 · github.com
- 24TP
2019 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →