An token refresh library for dart. This package exposes the core components that are common to various refresh token implementations (REST, GraphQL, etc...).
Package selection guidance compiled from public package information, community data, and project usage.
Fresh is a Dart library designed to manage token refresh workflows across REST and GraphQL APIs. It provides reusable components for handling authentication tokens, ensuring secure and consistent token renewal without duplicating logic. The package abstracts common patterns like token expiration detection, automatic refresh requests, and error handling, making it easier to implement robust authentication flows in Flutter and other Dart applications. Built with modularity in mind, Fresh supports multiple platforms including mobile, web, and desktop.
Use cases
Handling expired JWT tokens
Automating token refresh in REST APIs
Managing authentication state in GraphQL clients
Securing API calls with valid tokens
Implementing resilient auth flows
Key features
Modular token refresh architecture
Support for REST and GraphQL
Cross-platform compatibility
Automatic retry on failed requests
Configurable refresh strategies
Suitable for
Flutter apps with API authentication
Applications using JWT or similar tokens
Developers building reusable auth systems
Projects requiring secure token management
Multi-platform applications
Considerations
Requires custom implementation for specific auth endpoints
May need integration with HTTP clients like dio or http
Not a full auth solution but a refresh utility
Depends on proper backend token refresh setup
Limited to token refresh—not login or logout
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Fresh 🍋
A collection of packages for automatic token refresh in Dart and Flutter. Fresh handles refreshing, caching, and attaching authentication tokens transparently so your API calls just work.
Why Fresh?
Token-based authentication seems simple until you handle the edge cases: tokens expire mid-session, multiple requests fail at the same time triggering duplicate refreshes, refresh tokens get revoked, and you need to route users to login when auth is lost. Fresh handles all of this so you don't have to.
No more manual 401 handling scattered across your codebase
No more race conditions when concurrent requests trigger simultaneous refreshes
No more stale tokens causing request failures - expired tokens are refreshed proactively before the request is even sent