ketting
The HATEOAS client for javascript (by badgateway)
browser
A HAL browser middleware for node.js (by curveball)
Our great sponsors
| ketting | browser | |
|---|---|---|
| 5 | 3 | |
| 542 | 43 | |
| 2.0% | - | |
| 5.6 | 8.3 | |
| 6 months ago | 3 months ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
ketting
Posts with mentions or reviews of ketting.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-14.
-
What's the typical way for a RESTful API to tell clients what content types are supported?
So Accept does work as a response header, specifically for this case. I usually prefer to not do this extra request though. Since you're already using a hypermedia format, usually you can also include a type parameter. HAL supports this for example. Would strongly suggest you don't invent your own format. I do a lot of hypermedia APIs, we also wrote a client
-
What could be the reason why you would still chose REST over GraphQL or gRPC for your API?
I prefer REST and using HATEOAS. Its fantastic, check it out: https://restfulapi.net/hateoas/ And using tooling like https://github.com/badgateway/react-ketting and https://github.com/badgateway/ketting Makes everything extremely clean and much more simple.
-
Roy Fielding's Misappropriated REST Dissertation
I'm trying to (help) solve this:
https://github.com/badgateway/ketting - react-query: A magical way to fetch data in React
-
Typed fetch requests
Our client is open source and we've been developing it for over 4 years: https://github.com/badgateway/ketting , plus we got react bindings so you can also use resource as such:
browser
Posts with mentions or reviews of browser.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-26.
- How To Present Backend Demos
-
Looking for an admin system to manage my API, something that I can configure to consume my API and present the data in a nice way.
Not sure if it's exactly what you're looking for, and this would have to be adapted for Nest.js, but here it is: https://github.com/curveball/browser/
-
Roy Fielding's Misappropriated REST Dissertation
https://github.com/curveball/browser
What are some alternatives?
When comparing ketting and browser you can also consider the following projects:
ky - 🌳 Tiny & elegant JavaScript HTTP client based on the browser Fetch API
express-openapi-validator - 🦋 Auto-validates api requests, responses, and securities using ExpressJS and an OpenAPI 3.x specification
react-ketting - Ketting bindings for React
API Platform - Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
appy - A functional wrapper around Fetch API
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
dragon - ⚡Fast , simple expressive web framework for deno 🦕.
bodyparser - A middleware to parse JSON and Text bodies.
connect-go - Moved to https://github.com/connectrpc/connect-go