Persist-And-Sync Zustand Store

Zustand middleware to easily persist and sync Zustand state between tabs/windows/iframes (Same Origin)

Motivation: Recently I got caught up in several issues working with the persist middleware and syncing tabs with Zustand. This is a simple lightweight middleware to persist and instantly share state between tabs or windows

• ✅ 🐙 ~ 1 kB size cross-tab state sharing + persistence for zustand
• ✅ Full TypeScript Support
• ✅ solid reliability in 1 writing and n reading tab scenarios (with changing writing tab)
• ✅ Fire and forget approach of always using the latest state. Perfect for single-user systems
• ✅ Share state between multiple browsing contexts
• ✅ Additional control over which fields to persist-and-sync and which to ignore
• ✅ Optimized for performance using memoization and closures.
• ✅ Update options at runtime by setting __persistNSyncOptions in your store.

Install

1$ pnpm add persist-and-sync

or

1$ npm install persist-and-sync

or

1$ yarn add persist-and-sync

Usage

Add the middleware while creating the store and the rest will be taken care.

1import { create } from "zustand";
2import { persistNSync } from "persist-and-sync";
3
4type MyStore = {
5	count: number;
6	set: (n: number) => void;
7};
8
9const useStore = create<MyStore>(
10	persistNSync(
11		set => ({
12			count: 0,
13			set: n => set({ count: n }),
14		}),
15		{ name: "my-example" },
16	),
17);

⚡🎉Boom! Just a couple of lines and your state perfectly syncs between tabs/windows and it is also persisted using localStorage!

Advanced Usage (Customizations)

PersistNSyncOptions

In several cases, you might want to exclude several fields from syncing. To support this scenario, we provide a mechanism to exclude fields based on a list of fields or regular expressions.

1type PersistNSyncOptionsType = {
2	name: string;
3	/** @deprecated */
4	regExpToIgnore?: RegExp;
5	include?: (string | RegExp)[];
6	exclude?: (string | RegExp)[];
7	storage?: "localStorage" | "sessionStorage" | "cookies" /** Added in v1.1.0 */;
8};

Example

1export const useMyStore = create<MyStoreType>()(
2	persistNSync(
3		set => ({
4			count: 0,
5			_count: 0 /** skipped as it is included in exclude array */,
6			setCount: count => {
7				set(state => ({ ...state, count }));
8			},
9			set_Count: _count => {
10				set(state => ({ ...state, _count }));
11			},
12		}),
13		{ name: "example", exclude: ["_count"] },
14	),
15);

It is good to note here that each element of include and exclude array can either be a string or a regular expression. To use regular expression, you should either use new RegExp() or /your-expression/ syntax. Double or single quoted strings are not treated as regular expression. You can specify whether to use either "localStorage", "sessionStorage", or "cookies" to persist the state - default "localStorage". Please note that "sessionStorage" is not persisted. Hence can be used for sync only scenarios.

Updating options at runtime

Since version 1.2, you can also update the options at runTime by setting __persistNSyncOptions in your Zustand state.

Example

1interface StoreWithOptions {
2	count: number;
3	_count: number;
4	__persistNSyncOptions: PersistNSyncOptionsType;
5	setCount: (c: number) => void;
6	set_Count: (c: number) => void;
7	setOptions: (__persistNSyncOptions: PersistNSyncOptionsType) => void;
8}
9
10const defaultOptions = { name: "example", include: [/count/], exclude: [/^_/] };
11
12export const useStoreWithOptions = create<StoreWithOptions>(
13	persistNSync(
14		set => ({
15			count: 0,
16			_count: 0 /** skipped as it matches the regexp provided */,
17			__persistNSyncOptions: defaultOptions,
18			setCount: count => set(state => ({ ...state, count })),
19			set_Count: _count => set(state => ({ ...state, _count })),
20			setOptions: __persistNSyncOptions => set(state => ({ ...state, __persistNSyncOptions })),
21		}),
22		defaultOptions,
23	),
24);

Clear Storage

Starting from version 1.2, you can also clear the persisted data by calling clearStorage function. It takes name of your store (name passed in options while creating the store), and optional storageType parameters.

1import { clearStorage } from "persist-and-sync";
2
3...
4	clearStorage("my-store", "cookies");
5...

Legacy / Deprecated

Ignore/filter out fields based on regExp

In several cases, you might want to exclude several fields from syncing. To support this scenario, we provide a mechanism to exclude fields based on regExp. Just pass regExpToIgnore (optional - default -> undefined) in the options object.

1// to ignore fields containing a slug
2persistNSync(
3    set => ({
4      count: 0,
5      slugSomeState: 1,
6      slugSomeState2: 1,
7      set: n => set({ count: n }),
8    }),
9    { name: "my-channel", regExpToIgnore: /slug/ },
10    // or regExpToIgnore: new RegExp('slug')
11    // Use full power of regExp by adding `i` and `g` flags
12  ),

For more details about regExp check out - JS RegExp

Exact match

For exactly matching a parameter/field use /^your-field-name$/. ^ forces match from the first character and similarly, $ forces match until the last character.

Ignore multiple fields with exact match

use regExpToIgnore: /^(field1|field2|field3)$/

🤩 Don't forget to star this repo!

Want a hands-on course for getting started with Turborepo? Check out React and Next.js with TypeScript and The Game of Chess with Next.js, React and TypeScrypt

License

Licensed as MIT open source.

---

with 💖 by Mayank Kumar Chaudhari