Skip to content

Releases: BetterTyped/hyper-fetch

hyper-fetch-v7.0.2

29 Jun 10:11
Compare
Choose a tag to compare

7.0.2 (2025-06-29)

Bug Fixes

  • 🐛 fixed defaults for generic types of requests (c20f1fb)

hyper-fetch-v7.0.1

26 Jun 09:39
Compare
Choose a tag to compare

7.0.1 (2025-06-26)

Bug Fixes

hyper-fetch-v7.0.0

25 Jun 16:57
Compare
Choose a tag to compare

HyperFetch v7.0.0 Release Notes (2025-06-25)

This is a major release that brings a completely revamped developer experience, a new plugin system, and a host of other
improvements and breaking changes. The entire library has been modernized to provide a more robust and flexible
data-fetching solution.


✨ Highlights

🚀 Hyper Flow: The New DevTools

We are thrilled to introduce Hyper Flow, a brand-new, standalone Electron application that provides a powerful and
intuitive UI for debugging and visualizing your HyperFetch requests.

  • Real-time Monitoring: See all your requests, cache, and queue state in real-time.
  • Detailed Request Inspection: Dive deep into individual requests to see their data, headers, and timings.
  • Cache and Queue Management: Inspect and manage your cached data and request queues.
  • Data Visualization: Visualize your data flows and understand how your app interacts with your APIs.
  • And much more...

🔌 New Plugin System

HyperFetch now has a powerful plugin system that allows you to extend its functionality. The first official plugin is
@hyper-fetch/plugin-devtools, which connects your application to the new Hyper Flow DevTools.

ESLint Plugin

A new ESLint plugin (@hyper-fetch/eslint-plugin-hyper-fetch) is now available to help you enforce best practices and
avoid common pitfalls when using HyperFetch.

🧪 Testing Module

The new @hyper-fetch/testing module makes it easier than ever to test your data-fetching logic. It provides
out-of-the-box mocking for:

  • HTTP requests
  • GraphQL queries and mutations
  • Server-Sent Events (SSE)
  • WebSockets

💥 Breaking Changes

This release introduces several breaking changes. Please review them carefully before upgrading.

Core (@hyper-fetch/core)

  • Client and Request Creation:
    • The new Client() constructor is deprecated. Use the new createClient() function instead.
    • Use the new client.createRequest() method to build your requests. This new method provides improved type inference
      and a more fluent API.
  • TypeScript Strict Mode: The library now fully supports TypeScript's strict mode. This may cause type errors in
    your existing codebase if you are not using strict mode.
  • Immer Integration: We now use Immer for immutable state management. This should be a transparent change for most
    users, but it's a significant internal update.
  • Cache and Dispatcher: The caching and request dispatching systems have been heavily refactored for better
    performance and reliability.
  • cacheTime and staleTime: We've introduced cacheTime and staleTime options for more granular control over
    caching, similar to what you might know from other data-fetching libraries.
  • Default HTTP Adapter: The default HTTP adapter is now included in the @hyper-fetch/core package. You no longer
    need to install a separate adapter for basic HTTP requests.

React (@hyper-fetch/react)

  • Hooks API: The React hooks (useFetch, useSubmit, etc.) have been refactored. While the core functionality
    remains the same, there might be subtle changes in behavior and return values.
  • Hydration: We've introduced new and improved APIs for server-side rendering (SSR) hydration.
  • Provider: The ConfigProvider has been renamed to HyperFetchProvider for clarity.

Sockets (@hyper-fetch/sockets)

  • Adapters: The socket implementation has been completely rewritten. We now provide two separate adapters:
    • @hyper-fetch/socket-adapter-sse for Server-Sent Events.
    • @hyper-fetch/socket-adapter-ws for WebSockets.
  • Improved Error Handling: Error handling for socket connections has been significantly improved.

Adapters (@hyper-fetch/adapter-*)

  • All adapters (axios, firebase, firebase-admin, graphql) have been updated to be compatible with the new core
    changes. You will need to update them to their latest versions.

Build System

  • We have dropped support for CommonJS (CJS). HyperFetch is now an ESM-only library. You will need to ensure your build
    system is configured to handle ESM packages.

📦 New Packages

  • @hyper-fetch/hyper-flow: The new DevTools application.
  • @hyper-fetch/plugin-devtools: The plugin to connect your app to Hyper Flow.
  • @hyper-fetch/eslint-plugin-hyper-fetch: The new ESLint plugin.
  • @hyper-fetch/testing: The new testing module.

Upgrading

To upgrade to v6.0.0, you will need to update all the HyperFetch packages you are using to their latest versions.

npm install @hyper-fetch/core@latest @hyper-fetch/react@latest ...
# or
yarn add @hyper-fetch/core@latest @hyper-fetch/react@latest ...

We recommend carefully reviewing the updated documentation and examples to understand how to adapt your code to the new
APIs.

hyper-fetch-v6.0.1

19 Mar 17:08
Compare
Choose a tag to compare

6.0.1 (2025-03-19)

Bug Fixes

  • 🐛 codegen better errors and process.exit(0) (13e90d6)
  • 🐛 Rerendering with initial fetching state (cc329b9), closes #94

hyper-fetch-v6.0.0

05 Dec 14:05
Compare
Choose a tag to compare

6.0.0 (2024-12-05)

Bug Fixes

BREAKING CHANGES

hyper-fetch-v5.7.6-beta.1

04 Dec 10:15
Compare
Choose a tag to compare
Pre-release

5.7.6-beta.1 (2024-12-04)

Bug Fixes

hyper-fetch-v5.7.5

23 May 13:07
9fe13e5
Compare
Choose a tag to compare

5.7.5 (2024-05-23)

Bug Fixes

  • Update package.json to fix typescript issue (#88) (9fe13e5)

hyper-fetch-v5.7.4

12 Jan 17:15
Compare
Choose a tag to compare

5.7.4 (2024-01-12)

Bug Fixes

  • 🐛 Minor bux fix + test fixes (f1da22a)

hyper-fetch-v5.7.3

12 Oct 17:39
de4a2fe
Compare
Choose a tag to compare

5.7.3 (2023-10-12)

Bug Fixes

  • 🐛 Response mappers now affect the initial state on change (#75) (de4a2fe)

hyper-fetch-v5.7.2

04 Oct 15:00
c36a581
Compare
Choose a tag to compare

5.7.2 (2023-10-04)

Bug Fixes

  • use correct path for types in core package.json (#74) (c36a581)