We believe that hypermedia APIs, APIs who's responses include links and forms, significantly reduces to coupling between the client and server, making them easier to evolve.
The packages/fetch-link library, and the libraries its
built on, adapts the fetch API to work with
RFC8288 Links. It parses Link and
Link-Template headers, providing them via links() method on the Response, and
it can use links and request inputs, allowing call chaining.
@windyroad/adapt-fetch-inputA library for adapting fetch inputs@windyroad/decorate-fetch-response: A library for decorating fetch responses.@windyroad/fetch-fragment: A fetch library that can retrieve json fragments@windyroad/fetch-link: A library that adapts the fetch API to work with RFC8288 Link objects.@windyroad/ofetch-link: A library that adapts the ofetch library to work with RFC8288 Link objects.@windyroad/link-header: Parse & format HTTP link headers according to RFC8288@windyroad/wrap-fetch: A library for wrapping fetch, so requests and responses can be modified.@windyroad/eslint-config: XO config for the Windy Road style guide.
Contributions are welcome! Please see our contributing guidelines for more information.
Very Fetching is lovingly licensed under the MIT License. ❤️
