endograph/redux-persist

persist and rehydrate a redux store

View on GitHub ↗Jump to charts ↓Open shareable report →

endograph/redux-persist has 12k+ stars and 800+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 3rd, 2026
Created on July 23rd, 2015
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 840
Total Stargazers: 12,949 (+0)
Total Subscribers: 83 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.4 days
Mean response time: 750.5 days
90th percentile: 2658.8 days
Tracked items: 528

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (318)
  • bug report (6)
  • usability (6)
  • docs (4)
  • flow (4)
  • question (4)
  • v5 (4)
  • feature request (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Redux Persist is a middleware library that persists and rehydrates a Redux store.

The tool solves the problem of losing application state when users refresh or close their browser. It works by wrapping your reducer with persistReducer and your store with persistStore, which automatically save state changes to storage and restore them on app startup. For React applications, PersistGate delays UI rendering until persisted state has been retrieved, preventing flash-of-content issues. The library supports multiple storage backends and provides fine-grained control over what gets persisted through whitelist and blacklist configuration.

Developers should use this tool if they need client-side state persistence in a Redux application. It suits projects where maintaining user state across sessions is important, from simple single-page apps to complex applications with nested persists. The library requires deliberate configuration of state reconciliation strategy, as the default merges only one level of state and developers must choose the appropriate reconciler for their state shape. The tool provides methods to manually control persistence timing through manualPersist mode, useful when storage backends are not immediately ready.

The project has resumed active maintenance after a period of inactivity. A triage process is underway to address accumulated issues. Documentation covers basic usage, nested persists, and hot module replacement, with code splitting examples marked as coming soon. The API surface includes core functions for wrapping reducers and stores, along with a persistor object offering methods to purge state, flush pending writes, pause persistence, and resume it on demand.