@ibnlanre/portal
is a state management library designed to bridge the gap between simple state hooks and complex state machines. It provides an intuitive, type-safe approach to state management that grows with your application’s needs.
Perfect for teams that:
Whether you’re building a small React component or a large-scale application, @ibnlanre/portal
adapts to your needs without forcing specific architectural patterns or unnecessary complexity.
createStore()
createContextStore()
useAsync
useSync
useVersion
InferType
@ibnlanre/portal
offers powerful features for efficient state management:
📦 Flexible Store Types
🔄 Intuitive State Management
$get
, $set
, and $act
⚛️ Seamless React Integration
$use
hookcreateContextStore
🔌 Built-in State Persistence
🛠️ Advanced Capabilities
This section guides you through setting up @ibnlanre/portal
in your project.
Before you begin, ensure your development environment includes:
You can add @ibnlanre/portal
to your project using a package manager or by including it from a CDN.
Run one of the following commands, depending on your package manager:
npm
npm install @ibnlanre/portal
pnpm
pnpm add @ibnlanre/portal
yarn
yarn add @ibnlanre/portal
The library includes TypeScript definitions, so no separate @types
package is needed.
For projects that don’t use a package manager (e.g., simple HTML pages or online playgrounds), you can include @ibnlanre/portal
from a CDN:
Skypack
<script type="module">
import { createStore } from "https://cdn.skypack.dev/@ibnlanre/portal";
// Use createStore and other exports here
</script>
unpkg
<script src="https://unpkg.com/@ibnlanre/portal"></script>
<!-- The library will be available globally, e.g., window.Portal.createStore -->
jsDelivr
<script src="https://cdn.jsdelivr.net/npm/@ibnlanre/portal"></script>
<!-- The library will be available globally, e.g., window.Portal.createStore -->
Understanding these core concepts will help you use @ibnlanre/portal
effectively.
A store is an object that holds your application’s state. It allows you to read the state, update it, and subscribe to changes. @ibnlanre/portal
stores can hold any kind of data, from simple primitive values to complex, nested objects.
Store Type | Description | Example Initial State |
---|---|---|
Primitive Store | Manages a single primitive value (string, number, boolean, null, undefined) | 0 , "Alex" , true |
Composite Store | Manages an object with nested properties, each as a sub-store | { name: "Alex", age: 30 } |
@ibnlanre/portal
distinguishes between two main types of stores, created automatically based on the initial state you provide:
Primitive Store: Manages a single, primitive value (e.g., a string, number, boolean, null, or undefined). At times, it can also manage a single object as a primitive-like store, where the entire object is treated as a single value.
Composite Store: Manages an object, enabling nested state structures. Each property in a composite store’s initial object can itself become a store instance (either primitive or composite), allowing for granular state management and access.
name
, email
, address
) can be accessed and updated independently.Both store types share a consistent API for getting, setting, and subscribing to state.
@ibnlanre/portal
embraces immutability. When you update the state, the library creates a new state object instead of modifying the existing one. This helps prevent bugs and makes state changes predictable.
Tip: Stores are reactive. When a store’s state changes, any components or subscribers listening to that store (or its parts) are notified, allowing your UI to update automatically.
By default, when you update objects in @ibnlanre/portal
, the library performs partial updates (merging). This means only the properties you specify are changed, while other properties remain unchanged. However, sometimes you want to treat an object as a single value that should be completely replaced when updated.
The atom()
function allows you to mark objects as atomic, which changes their update behavior from merging to complete replacement.
Regular objects (default behavior - merging):
import { createStore } from "@ibnlanre/portal";
const settingsStore = createStore({
theme: "dark",
fontSize: 16,
notifications: true,
});
// Partial update - only changes the theme, keeps other properties
settingsStore.$set({ theme: "light" });
console.log(settingsStore.$get());
// Output: { theme: "light", fontSize: 16, notifications: true }
Atomic objects (complete replacement):
import { createStore, atom } from "@ibnlanre/portal";
const preferencesStore = createStore({
userSettings: atom({
theme: "dark",
fontSize: 16,
notifications: true,
}),
});
// Complete replacement - replaces the entire object
preferencesStore.userSettings.$set({ theme: "light" });
console.log(preferencesStore.userSettings.$get());
// Output: { theme: "light" }
// Note: fontSize and notifications are gone
Atomic objects are particularly useful for:
atom()
Syntax:
atom<T extends object>(value: T): T
value
: The object to mark as atomicBasic Example:
import { createStore, atom } from "@ibnlanre/portal";
const appStore = createStore({
// Regular object - supports partial updates
user: {
name: "Alice",
email: "alice@example.com",
age: 30,
},
// Atomic object - complete replacement only
apiConfig: atom({
baseUrl: "https://api.example.com",
timeout: 5000,
retries: 3,
}),
});
// Partial update on regular object
appStore.user.$set({ name: "Bob" });
console.log(appStore.user.$get());
// Output: { name: "Bob", email: "alice@example.com", age: 30 }
// Complete replacement on atomic object
appStore.apiConfig.$set({ baseUrl: "https://api.dev.com" });
console.log(appStore.apiConfig.$get());
// Output: { baseUrl: "https://api.dev.com" }
// Note: timeout and retries are removed
1. Mixed regular and atomic objects:
import { createStore, atom } from "@ibnlanre/portal";
const gameStore = createStore({
player: {
name: "Player1",
score: 100,
inventory: {
gold: 50,
items: ["sword", "potion"],
},
},
// Game settings are treated as a complete unit
gameSettings: atom({
difficulty: "medium",
soundEnabled: true,
graphicsQuality: "high",
}),
});
// Partial update on player (merges with existing data)
gameStore.player.$set({ score: 150 });
// player.name and player.inventory remain unchanged
// Complete replacement of game settings
gameStore.gameSettings.$set({ difficulty: "hard" });
// soundEnabled and graphicsQuality are removed
2. Atomic objects with functional updates:
import { createStore, atom } from "@ibnlanre/portal";
const themeStore = createStore({
currentTheme: atom({
primary: "#007bff",
secondary: "#6c757d",
background: "#ffffff",
}),
});
// Use functional updates for conditional logic
themeStore.currentTheme.$set((currentTheme) => {
if (currentTheme.background === "#ffffff") {
// Switch to dark theme (complete replacement)
return {
primary: "#0d6efd",
secondary: "#495057",
background: "#212529",
};
} else {
// Switch to light theme (complete replacement)
return {
primary: "#007bff",
secondary: "#6c757d",
background: "#ffffff",
};
}
});
3. Nested atomic objects:
import { createStore, atom } from "@ibnlanre/portal";
const userStore = createStore({
profile: {
name: "John Doe",
// Preferences are atomic - complete replacement
preferences: atom({
language: "en",
timezone: "UTC",
notifications: true,
}),
// Regular object - partial updates
contact: {
email: "john@example.com",
phone: "+1234567890",
},
},
});
// Partial update on contact
userStore.profile.contact.$set({ email: "newemail@example.com" });
// phone number remains unchanged
// Complete replacement of preferences
userStore.profile.preferences.$set({ language: "fr", timezone: "CET" });
// notifications setting is removed
1. atom()
is idempotent:
import { atom } from "@ibnlanre/portal";
const config = { api: "https://api.com", version: "v1" };
const atomic1 = atom(config);
const atomic2 = atom(atomic1); // Safe to call multiple times
console.log(atomic1 === atomic2); // true
2. Atomic objects preserve normal JavaScript behavior:
import { atom } from "@ibnlanre/portal";
const settings = atom({
theme: "dark",
lang: "en",
});
// Normal object operations work as expected
console.log(Object.keys(settings)); // ["theme", "lang"]
console.log(settings.theme); // "dark"
console.log(JSON.stringify(settings)); // '{"theme":"dark","lang":"en"}'
3. Atomic behavior affects subscriptions:
import { createStore, atom } from "@ibnlanre/portal";
const store = createStore({
regularData: { a: 1, b: 2 },
atomicData: atom({ x: 10, y: 20 }),
});
store.regularData.$sub((data) => {
console.log("Regular data changed:", data);
});
store.atomicData.$sub((data) => {
console.log("Atomic data changed:", data);
});
store.regularData.$set({ a: 5 });
// Logs: "Regular data changed: { a: 5, b: 2 }"
store.atomicData.$set({ x: 50 });
// Logs: "Atomic data changed: { x: 50 }"
// Note: y property is gone
Understanding atomic objects helps you control exactly how your data updates, leading to more predictable state management and fewer bugs related to unexpected partial updates.
@ibnlanre/portal
is designed to work with minimal configuration. The primary configuration points are:
createStore()
, you provide the initial state. This is the main configuration for a store’s structure and default values.Refer to the Persist state section for detailed configuration of each adapter.
This section provides a comprehensive reference for the @ibnlanre/portal
API, with detailed explanations and examples.
createStore()
The createStore()
function is the primary way to initialize a new store. For specific scenarios or finer control, you can also use the direct store creation functions createPrimitiveStore()
and createCompositeStore()
.
createStore()
Syntax:
createStore<S>(initialState: S | Promise<S>): Store<S>
initialState
: The initial value for the store.
PrimitiveStore<S>
is created.CompositeStore<S>
is created, allowing for nested properties to be accessed as individual stores.Promise
is provided, the store will be initialized with the resolved value of the promise. The store will be empty until the promise resolves. The resolved value is treated as a single entity; if it’s an object, it becomes the state of a primitive-like store, not a composite store with nested properties.Store
instance, which can be a PrimitiveStore<S>
or CompositeStore<S>
depending on initialState
.Examples:
Creating a primitive store:
import { createStore } from "@ibnlanre/portal";
const countStore = createStore(0);
console.log(countStore.$get()); // Output: 0
const messageStore = createStore("Hello, world!");
console.log(messageStore.$get()); // Output: "Hello, world!"
Creating a composite store:
import { createStore } from "@ibnlanre/portal";
const userStore = createStore({
id: 1,
name: "Alex Johnson",
email: "alex@example.com",
address: {
street: "123 Main St",
city: "Anytown",
},
});
console.log(userStore.name.$get()); // Output: "Alex Johnson"
console.log(userStore.address.city.$get()); // Output: "Anytown"
Creating a store with asynchronous initialization:
import { createStore } from "@ibnlanre/portal";
async function fetchUserData(): Promise<{ id: number; name: string }> {
return new Promise((resolve) => {
setTimeout(() => resolve({ id: 1, name: "Fetched User" }), 1000);
});
}
const userProfileStore = await createStore(fetchUserData());
// The store is now initialized as a primitive store with the fetched data.
// Note: userProfileStore holds { id: 1, name: "Fetched User" } as a single value.
// It's not created as a composite store despite being an object.
console.log(userProfileStore.$get()); // Output: { id: 1, name: "Fetched User" }
createPrimitiveStore()
Creates a store specifically for a single, primitive value (string, number, boolean, null, undefined, symbol, bigint).
Syntax:
createPrimitiveStore<S extends Primitives>(initialState: S): PrimitiveStore<S>
initialState
: The initial primitive value.PrimitiveStore<S>
instance.When to use:
createStore()
type inference for primitives might need disambiguation (though generally robust).Example:
import { createPrimitiveStore } from "@ibnlanre/portal";
const isActiveStore = createPrimitiveStore(false);
console.log(isActiveStore.$get()); // false
createCompositeStore()
Creates a store specifically for an object, enabling nested state structures.
Syntax:
createCompositeStore<S extends GenericObject>(initialState: S): CompositeStore<S>
initialState
: The initial object. Each property can become a nested store.CompositeStore<S>
instance.When to use:
Example:
import { createCompositeStore } from "@ibnlanre/portal";
const userDetailsStore = createCompositeStore({
username: "guest",
permissions: { read: true, write: false },
});
console.log(userDetailsStore.username.$get()); // "guest"
userDetailsStore.permissions.write.$set(true);
Note: Using
createStore()
is generally preferred as it automatically determines whether to create a primitive or composite store based on the initial state.
createContextStore()
The createContextStore()
function creates React Context-based stores that solve a common problem: initializing stores with dynamic values that come from props or external sources. This is particularly useful when you need to create stores that depend on runtime data rather than static initial values.
Key Benefits:
The Problem it Solves:
Global stores are typically created outside of the React component lifecycle, so they can’t be initialized with values from props or context. With a global store, you’d need to:
useEffect
in every component that needs itcreateContextStore
eliminates this boilerplate by allowing you to pass a function that receives the context data needed before the store is initialized.
Syntax:
createContextStore<Context, ContextStore>(
initializer: (context: Context) => ContextStore
): [StoreProvider, useStore]
initializer
: A function that receives the context value and returns a store instance[StoreProvider, useStore]
Basic Example:
import { createContextStore, createStore } from "@ibnlanre/portal";
interface UserProps {
userId: string;
theme: "light" | "dark";
}
// Create a context store for user settings
const [UserProvider, useUserStore] = createContextStore(
(context: UserProps) => {
return createStore(context);
}
);
function UserProfile() {
const store = useUserStore();
const { userId, theme } = store.$get();
return (
<div style=>
<p>User ID: {userId}</p>
<p>Theme: {theme}</p>
</div>
);
}
function App(props: UserProps) {
return (
<UserProvider value={props}>
{/* The UserProfile component can now access the userId and theme from the context */}
<UserProfile />
</UserProvider>
);
}
<App userId="123" theme="dark" />;
Advanced Example with Actions:
import { createContextStore, createStore, combine } from "@ibnlanre/portal";
type CounterContext = { initialCount: number };
const [CounterProvider, useCounterStore] = createContextStore(
(context: CounterContext) => {
const store = useSync(() => {
const initialState = { count: context.initialCount };
const actions = {
increment: () => {
counterStore.count.$set((prev) => prev + 1);
},
decrement: () => {
counterStore.count.$set((prev) => prev - 1);
},
reset: () => {
counterStore.count.$set(context.initialCount);
},
};
const counterStore = createStore(combine(initialState, actions));
return counterStore;
}, [context.initialCount]);
return store;
}
);
function Counter() {
const store = useCounterStore();
const [count] = store.count.$use();
return (
<div>
<span>Count: {count}</span>
<button onClick={store.increment}>+</button>
<button onClick={store.decrement}>-</button>
<button onClick={store.reset}>Reset</button>
</div>
);
}
function App() {
return (
<CounterProvider value=>
<Counter />
</CounterProvider>
);
}
Use Cases:
Note: The factory function passed to
createContextStore
runs on every render. You’re responsible for memoizing values if needed. This design gives you complete freedom to use any hooks or memoization strategy within the factory function.
All store instances, whether primitive or composite, provide a core set of methods for interacting with the state.
$get()
Retrieves the current state of the store. Optionally, you can provide a selector function to compute a derived value from the state without altering the stored state.
Syntax:
$get(): S
$get<R>(selector: (currentState: S) => R): R
selector
(optional): A function that takes the current state (S
) as an argument and returns a derived value (R
).S
) if no selector is provided, or the derived value (R
) if a selector is provided.Examples:
Getting the current state:
const countStore = createStore(10);
const currentCount = countStore.$get(); // 10
const userStore = createStore({ name: "Alex", role: "admin" });
const currentUser = userStore.$get(); // { name: "Alex", role: "admin" }
const userName = userStore.name.$get(); // "Alex"
Getting a derived value using a selector:
const countStore = createStore(10);
const doubledCount = countStore.$get((count) => count * 2); // 20
console.log(countStore.$get()); // 10 (original state is unchanged)
const userStore = createStore({ firstName: "Alex", lastName: "Johnson" });
const fullName = userStore.$get(
(user) => `${user.firstName} ${user.lastName}`
); // "Alex Johnson"
$set()
Updates the store’s state. You can pass a new value directly or provide an update function that receives the previous state and returns the new state.
For composite stores holding objects, $set
performs a deep partial update. This means you only need to provide the properties you want to change, and @ibnlanre/portal
will merge them intelligently with the existing state.
Syntax:
$set(newValue: S): void
$set(updater: (prevState: S) => S): void
newValue
: The new state value to set directly.updater
: A function that takes the previous state (S
) as an argument and returns the new state (S
).void
.Examples:
Setting a new value directly (Primitive Store):
const countStore = createStore(0);
countStore.$set(5);
console.log(countStore.$get()); // 5
Updating using a function (Primitive Store):
const countStore = createStore(5);
countStore.$set((prevCount) => prevCount + 1);
console.log(countStore.$get()); // 6
Partial update on a Composite Store:
const settingsStore = createStore({
theme: "light",
fontSize: 12,
notifications: true,
});
// Update only theme and fontSize; notifications is preserved.
settingsStore.$set({ theme: "dark", fontSize: 14 });
// settingsStore.$get() is now { theme: "dark", fontSize: 14, notifications: true }
// Functional partial update
settingsStore.$set((prevSettings) => ({
...prevSettings, // Spread previous settings to preserve unspecified ones
fontSize: prevSettings.fontSize + 2, // Only update fontSize
}));
// settingsStore.$get() is now { theme: "dark", fontSize: 16, notifications: true }
Updating nested properties in a Composite Store:
const userStore = createStore({
profile: { name: "Alex", age: 30 },
role: "user",
});
// Update nested property directly
userStore.profile.name.$set("Alexandra");
console.log(userStore.profile.name.$get()); // "Alexandra"
// Update part of the nested object
userStore.profile.$set({ age: 31 }); // name is preserved
// userStore.profile.$get() is { name: "Alexandra", age: 31 }
Note on arrays: When a part of your state is an array, and you use $set
on the parent object containing that array, the entire array will be replaced if it’s part of the update object. To modify array elements (e.g., add or remove items), access the array store directly or use functional updates on that specific array store.
const listStore = createStore({ items: [1, 2, 3], name: "My List" });
// This replaces the entire 'items' array but preserves 'name'.
listStore.$set({ items: [4, 5, 6] });
// listStore.$get() is { items: [4, 5, 6], name: "My List" }
// To add an item, update the 'items' store directly.
listStore.items.$set((prevItems) => [...prevItems, 7]);
// listStore.items.$get() is now [4, 5, 6, 7]
$act()
Subscribes a callback function to state changes. The callback receives the new state (and optionally the old state) whenever it changes. This method returns an unsubscribe
function to stop listening for updates.
By default, the callback is invoked immediately with the current state upon subscription. To prevent this initial invocation, pass false
as the second argument.
Syntax:
$act(subscriber: (newState: S, oldState?: S) => void, immediate?: boolean): () => void
subscriber
: A function that is called when the state changes. It receives newState
and optionally oldState
.immediate
(optional, default true
): If true
, the subscriber
is called immediately with the current state. If false
, it’s only called on subsequent changes. (On the initial immediate call, oldState
is undefined
.)unsubscribe
function. Call this function to remove the subscription.Examples:
Basic subscription:
const nameStore = createStore("Alex");
const unsubscribe = nameStore.$act((newName, oldName) => {
console.log(`Name changed from "${oldName}" to "${newName}"`);
});
// Immediately logs: Name changed from "undefined" to "Alex"
// (oldState is undefined on the initial call if immediate: true)
nameStore.$set("Jordan"); // Logs: Name changed from "Alex" to "Jordan"
unsubscribe(); // Stop listening to changes
nameStore.$set("Casey"); // Nothing is logged
Subscription without immediate callback execution:
const statusStore = createStore("idle");
const unsubscribeNonImmediate = statusStore.$act((newStatus) => {
console.log(`Status updated to: ${newStatus}`);
}, false); // `false` prevents immediate call
statusStore.$set("active"); // Logs: "Status updated to: active"
// Unsubscribe to stop listening
unsubscribeNonImmediate();
Subscribing to a composite store:
const settingsStore = createStore({ theme: "light", volume: 70 });
// Setting up subscription to changes in settings
const unsubscribeSettings = settingsStore.$act((newSettings) => {
console.log("Settings updated:", newSettings);
});
// Changing the theme triggers the subscription
settingsStore.theme.$set("dark");
// Logs: Settings updated: { theme: "dark", volume: 70 }
unsubscribeSettings(); // Stop listening to changes
$key()
(CompositeStore only) Provides convenient access to deeply nested stores using a dot-separated string path. This method returns the nested store instance, allowing you to use its methods ($get
, $set
, $act
, $use
, $key
) directly.
Syntax:
$key<N extends Store<any>>(path: string): N
path
: A dot-separated string representing the path to the nested store (e.g., "user.preferences.theme"
). TypeScript provides autocompletion for valid paths.Store
instance (N
).Examples:
const appStore = createStore({
user: {
profile: {
name: "Alex",
email: "alex@example.com",
},
preferences: {
theme: "dark",
language: "en",
},
},
status: "active",
});
// Access nested stores using $key
const themeStore = appStore.$key("user.preferences.theme");
// Immediately get the current theme
console.log(themeStore.$get()); // "dark"
// Instantly update the theme
themeStore.$set("light");
// The update is reflected in the original store
console.log(appStore.user.preferences.theme.$get()); // "light"
$key
can be used on intermediate stores as well. For example, if you want to access a nested property like user.preferences.language
, you can do so directly:
// Accessing a nested store using $key
const preferencesStore = appStore.user.$key("preferences");
// Equivalent to appStore.$key("user.preferences.language")
const languageStore = preferencesStore.$key("language");
console.log(languageStore.$get()); // "en"
// Using methods on the store returned by $key
const unsubscribe = appStore.$key("user.preferences.theme").$act((newTheme) => {
console.log("Theme via $key:", newTheme);
});
// Triggers the subscription
appStore.user.preferences.theme.$set("blue");
unsubscribe();
$use()
(React Hook)Connects your React components to an @ibnlanre/portal
store. It works like React’s useState
hook, returning a tuple with the current state value (or a derived value) and a function to update the store’s state.
The $use
hook automatically subscribes the component to store changes and unsubscribes when the component unmounts, ensuring efficient re-renders.
Syntax:
$use(): [S, (newValue: S | ((prevState: S) => S)) => void]
$use<R>(
selector: (currentState: S) => R,
dependencies?: any[]
): [R, (newValue: S | ((prevState: S) => S)) => void]
selector
(optional): A function that takes the current store state (S
) and returns a transformed value (R
) for the component.dependencies
(optional): An array of dependencies for the selector
function. The selector is re-evaluated if any of these dependencies change (similar to React.useMemo
).currentStateOrDerivedValue
: The current state (S
) or the value returned by the selector
(R
).setStateFunction
: A function to update the store’s state. It accepts either a new value of type S
or an updater function (prevState: S) => S
.Examples:
Basic usage in a React component:
// src/stores/counter-store.ts
import { createStore } from "@ibnlanre/portal";
export const countStore = createStore(0);
// src/components/counter.tsx
import { countStore } from "../stores/counterStore";
function Counter() {
const [count, setCount] = countStore.$use();
return (
<div>
<p>Count: {count}</p>
<button onClick={() => setCount(count + 1)}>Increment</button>
<button onClick={() => setCount((prev) => prev - 1)}>
Decrement
</button>
<button onClick={() => setCount(0)}>Reset</button>
</div>
);
}
export default Counter;
Using a selector with $use
:
Selectors compute derived values from the store state without modifying the original state. The selector is only re-evaluated when necessary, optimizing performance.
// In your component:
// Assume counterStore holds a number.
const [displayCount, setCount] = counterStore.$use(
(currentCount) => `Current count is: ${currentCount}`
);
// If counterStore holds 0, displayCount is "Current count is: 0".
// setCount still expects a number to update the original counterStore.
return <p>{displayCount}</p>;
Using a selector with dependencies: This is useful when the selector depends on props or other state values. The dependencies can be any value, including primitive values, objects, or arrays. If the dependencies change, the selector will re-run to compute a new value.
import { useState } from "react";
import { displayStore } from "./store";
interface DisplayValueProps {
prefixFromProp: string;
}
function DisplayValue({ prefixFromProp }: DisplayValueProps) {
const [displayValue, setDisplayValue] = displayStore.$use(
(value) => `${prefixFromProp}${value}`,
[prefixFromProp] // Dependencies array
);
return (
<div>
<p>{displayValue}</p>
<input
type="text"
value={displayValue}
onChange={(e) => setDisplayValue(e.target.value)}
/>
</div>
);
}
Partial updates with objects using $use
:
When a store (or a part of a store accessed via $use
) holds an object, the setState
function returned by $use
supports partial updates. Provide an object with only the properties you want to change.
// store.ts
import { createStore } from "@ibnlanre/portal";
export const userStore = createStore({
name: "Alex",
age: 30,
city: "Anytown",
});
// user-profile.tsx
import { userStore } from "./store";
function UserProfile() {
const [user, setUser] = userStore.$use();
const handleAgeIncrease = () => {
setUser({ age: user.age + 1 }); // Only age is updated; name and city are preserved.
};
const handleNameChange = (event: React.ChangeEvent<HTMLInputElement>) => {
setUser({ name: event.target.value }); // Only name is updated.
};
return (
<div>
<input type="text" value={user.name} onChange={handleNameChange} />
<p>Age: {user.age}</p>
<p>City: {user.city}</p>
<button onClick={handleAgeIncrease}>Increase Age</button>
</div>
);
}
You can include functions within the initial state object of a composite store. These functions become methods on the store, allowing you to co-locate state logic (actions) with the state itself. This is useful for encapsulating complex state transitions.
When defining actions, to update state, you must use the variable that holds the store instance. For example, if your store is const store = createStore(...)
, you would use store.property.$set(...)
inside an action, not this.property.$set(...)
.
Examples:
Counter with actions:
import { createStore } from "@ibnlanre/portal";
const counterStore = createStore({
value: 0,
increment(amount: number = 1) {
// To update 'value', use 'counterStore.value'
counterStore.value.$set((prev) => prev + amount);
},
decrement(amount: number = 1) {
counterStore.value.$set((prev) => prev - amount);
},
reset() {
counterStore.value.$set(0);
},
});
counterStore.increment(5);
console.log(counterStore.value.$get()); // 5
counterStore.decrement();
console.log(counterStore.value.$get()); // 4
counterStore.reset();
console.log(counterStore.value.$get()); // 0
Reducer pattern: You can structure actions to follow a reducer pattern if that fits your application’s architecture.
import { createStore } from "@ibnlanre/portal";
type CounterAction =
| { type: "INCREMENT"; payload: number }
| { type: "DECREMENT"; payload: number }
| { type: "RESET" };
const counterStore = createStore({
value: 0,
dispatch(action: CounterAction) {
switch (action.type) {
case "INCREMENT":
// Use 'counterStore.value' to access $set
counterStore.value.$set((prev) => prev + action.payload);
break;
case "DECREMENT":
counterStore.value.$set((prev) => prev - action.payload);
break;
case "RESET":
counterStore.value.$set(0);
break;
}
},
});
counterStore.dispatch({ type: "INCREMENT", payload: 5 });
console.log(counterStore.value.$get()); // 5
counterStore.dispatch({ type: "RESET" });
console.log(counterStore.value.$get()); // 0
@ibnlanre/portal
allows you to define functions within your store that can be used as React custom hooks. This powerful feature enables you to co-locate complex, stateful logic—including side effects managed by useEffect
or component-level state from useState
directly with the store it relates to.
To create an action that functions as a hook, simply follow React’s convention:
use
createStore
This pattern leverages React’s own rules for hooks. It doesn’t prevent the function from being recreated on re-renders (which is normal React behavior), but it provides an excellent way to organize and attach reusable hook logic to your store instance.
⚠️ Note: These functions are not automatically memoized. To prevent recreating hook logic on every render, define your store at the module level whenever possible. If you need to create a store inside a React component, use the
useMemo
hook to ensure the store is created based on stable dependencies.
Example:
Let’s create a store with an action that uses useState
and useEffect
to automatically reset a message after a delay.
import { createStore } from "@ibnlanre/portal";
import { useState, useEffect } from "react";
export const notificationStore = createStore({
message: "",
setMessage(newMessage: string) {
notificationStore.message.$set(newMessage);
},
useAutoResetMessage(initialMessage: string, delay: number) {
const [internalMessage, setInternalMessage] = useState(initialMessage);
useEffect(() => {
if (internalMessage) {
const timer = setTimeout(() => {
setInternalMessage("");
}, delay);
return () => clearTimeout(timer);
}
}, [internalMessage, delay]);
useEffect(() => {
notificationStore.message.$set(internalMessage);
}, [internalMessage]);
return [internalMessage, setInternalMessage] as const;
},
});
Using the hook action in a component:
import { notificationStore } from "../stores/notification-store";
export function NotificationManager() {
const [message, setMessage] = notificationStore.useAutoResetMessage(
"Welcome!",
3000
);
const [globalMessage] = notificationStore.message.$use();
return (
<div>
<p>Current message (from hook state): {message}</p>
<p>Global message (from store): {globalMessage}</p>
<button onClick={() => setMessage("Resetting in 3 seconds")}>
Set Temporary Message
</button>
</div>
);
}
In this example, useAutoResetMessage
encapsulates its own state and side effects, just like a custom React hook, while still being able to interact with the global store. This pattern allows you to:
useAsync
The useAsync
hook provides a robust solution for handling asynchronous operations within your store actions. It automatically manages loading states, error handling, and data states, making it easy to work with promises and async functions.
Key Features:
loading
, error
, and data
statesBasic Usage:
import { createStore, useAsync } from "@ibnlanre/portal";
type UserProfile = {
id: string;
name: string;
email: string;
};
const userStore = createStore({
users: [] as UserProfile[],
profile: null as UserProfile | null,
useUsers: async () => {
const { data, loading, error } = useAsync(
async ({ signal }) => {
const response = await fetch("/api/users", { signal });
if (!response.ok) throw new Error("Failed to fetch users");
return response.json() as UserProfile[];
} // No dependencies, runs once on mount
);
if (data) userStore.users.$set(data);
return { userLoading: loading, userError: error };
},
useProfile: (userId: string) => {
const { data, loading, error } = useAsync(
async ({ signal }) => {
if (!userId) throw new Error("User ID is required");
const response = await fetch(`/api/users/${userId}`, { signal });
if (!response.ok) throw new Error("Failed to fetch user");
return response.json() as UserProfile;
},
[userId] // Dependency included in a list
);
if (data) userStore.profile.$set(data);
return { profileLoading: loading, profileError: error };
},
});
Usage in React component:
interface UserProfileComponentProps {
userId: string;
}
function UserProfileComponent({ userId }: UserProfileComponentProps) {
const { profileLoading: loading, profileError: error } =
userStore.useProfile(userId);
const [profile] = userStore.profile.$use();
if (loading) return <div>Loading...</div>;
if (error) return <div>Error: {error.message}</div>;
if (!profile) return <div>No profile found</div>;
return (
<div>
<h1>{profile.name}</h1>
<p>{profile.email}</p>
</div>
);
}
useSync
The useSync
hook provides a useMemo
implementation with deep dependency verification. It’s designed to compute and memoize values based on complex dependencies, with automatic re-computation when any part of the dependency tree changes.
Key Features:
Basic Usage:
import { createStore, useSync } from "@ibnlanre/portal";
const settingsStore = createStore({
fontSize: 16,
theme: "light" as "light" | "dark",
language: "en",
useDisplaySettings: () => {
const [theme] = settingsStore.theme.$use();
const [fontSize] = settingsStore.fontSize.$use();
const [language] = settingsStore.language.$use();
// This will only re-compute when theme, fontSize, or language change
return useSync(() => {
return {
cssVariables: {
"--theme": theme,
"--font-size": `${fontSize}px`,
"--language": language,
},
className: `theme-${theme} lang-${language}`,
styleObject: {
fontSize: fontSize,
colorScheme: theme,
},
};
}, [theme, fontSize, language]);
},
});
function ThemedComponent() {
const { className, styledObject, cssVariables } =
settingsStore.useDisplaySettings();
return (
<div className={className} style={styleObject}>
<p>Theme: {cssVariables["--theme"]}</p>
</div>
);
}
useVersion
The useVersion
hook provides deep dependency comparison through deep equality checking, making it ideal for complex state management scenarios. It allows you to track changes in deeply nested objects and arrays, providing both deep equality checking and version tracking for React hooks. It’s the foundational hook used internally by useAsync
and useSync
, but can also be used directly when you want to build custom hooks with deep dependency checking using native React hooks like useMemo
or useEffect
.
Key Features:
Basic Usage:
import { createStore, useVersion } from "@ibnlanre/portal";
import { useEffect } from "react";
const settingsStore = createStore({
theme: "light",
preferences: {
language: "en",
notifications: { email: true, push: false },
},
useWatchPreferences() {
const preferences = settingsStore.preferences.$get();
const version = useVersion(preferences);
useEffect(() => {
console.log("Preferences changed:", preferences);
// Sync preferences to external service
syncPreferencesToServer(preferences);
}, [version]);
return preferences;
},
});
The useVersion
hook is particularly useful when you want deep dependency tracking for custom hooks, or when native React hooks (useMemo
, useEffect
, useCallback
) need to respond to changes in complex objects or arrays.
Tip: Rather than using
useEffect
to sync the store state to an external service, consider using$act
for more efficient updates. This allows you to subscribe to changes in the store and react accordingly, while also providing a way to unsubscribe when no longer needed.
createContextStore
The createContextStore
function enables efficient global store management through React Context. It provides a powerful pattern for creating provider-based stores that can be initialized with external data and shared across component trees.
Key Features:
Basic Usage:
import { combine, createStore, createContextStore } from "@ibnlanre/portal";
// Define the context type
type AppContext = {
userId: string;
theme: "light" | "dark";
locale: string;
};
// Create the context scope
const [AppProvider, useAppStore] = createContextStore((context: AppContext) => {
const initialState = {
user: {
id: context.userId,
preferences: {
theme: context.theme,
locale: context.locale,
},
},
};
const actions = {
toggleTheme: () => {
store.user.preferences.theme.$set((previousTheme) => {
return previousTheme === "light" ? "dark" : "light";
});
},
updateTheme: (newTheme: "light" | "dark") => {
store.user.preferences.theme.$set(newTheme);
},
updateLocale: (newLocale: string) => {
store.user.preferences.locale.$set(newLocale);
},
};
const store = createStore(combine(initialState, actions));
return store;
});
Using the context-based store in a React application:
function App() {
const appContext: AppContext = {
userId: "user-123",
theme: "light",
locale: "en",
};
return (
<AppProvider value={appContext}>
<UserProfile />
<Settings />
</AppProvider>
);
}
function UserProfile() {
const store = useAppStore();
const [userId] = store.user.id.$use();
const [theme] = store.user.preferences.theme.$use();
return (
<div className={`profile theme-${theme}`}>
<h1>User ID: {userId}</h1>
</div>
);
}
function Settings() {
const store = useAppStore();
const [theme] = store.user.preferences.theme.$use();
return (
<div>
<button onClick={store.toggleTheme}>
Toggle Theme (Current: {theme})
</button>
</div>
);
}
combine()
The combine()
utility performs a deep merge between objects and now supports multiple sources for complex merging scenarios. It’s useful for unifying your initial state and actions into one cohesive structure before passing it into createStore.
Unlike shallow merging (such as Object.assign or object spread), combine()
:
Syntax:
// Single source merge
combine<Target extends Dictionary, Source>(target: Target, source: Source): Merge<Target, Source>
// Multiple sources merge
combine<Target extends Dictionary, Sources extends Dictionary[]>(target: Target, sources: Sources): Combine<Target, Sources>
target
: Base state or object.source
: Object containing actions or additional properties to merge.sources
: Array of objects to merge in sequence, with later sources taking precedence.Single Source Example:
import { createStore, combine } from "@ibnlanre/portal";
// Define the initial state
const initialState = {
isLoggedIn: false,
profile: {
email: "alex@example.com",
name: "Alex",
},
};
// Define actions separately
const actions = {
login(email: string) {
userStore.$set({
profile: { email },
isLoggedIn: true,
});
},
logout() {
userStore.$set({
isLoggedIn: false,
profile: { email: "", name: "" },
});
},
updateName(newName: string) {
userStore.profile.name.$set(newName);
},
};
// Combine initial state and actions into a single object
export const userStore = createStore(combine(initialState, actions));
Multiple Sources Example:
import { createStore, combine } from "@ibnlanre/portal";
// Base configuration
const baseConfig = {
api: {
baseUrl: "https://api.example.com",
timeout: 5000,
},
ui: {
theme: "light",
language: "en",
},
};
// Environment-specific overrides
const developmentConfig = {
api: {
baseUrl: "https://dev-api.example.com",
debug: true,
},
ui: {
showDebugInfo: true,
},
};
// User preferences
const userPreferences = {
ui: {
theme: "dark",
fontSize: 16,
},
notifications: {
email: true,
push: false,
},
};
// Combine all sources - later sources override earlier ones
const appConfig = combine(baseConfig, [developmentConfig, userPreferences]);
// Result will be:
// {
// api: {
// baseUrl: "https://dev-api.example.com", // from developmentConfig
// timeout: 5000, // from baseConfig
// debug: true // from developmentConfig
// },
// ui: {
// theme: "dark", // from userPreferences
// language: "en", // from baseConfig
// showDebugInfo: true, // from developmentConfig
// fontSize: 16 // from userPreferences
// },
// notifications: { // from userPreferences
// email: true,
// push: false
// }
// }
const configStore = createStore(appConfig);
You can initialize a store with state fetched asynchronously by passing an async
function (that returns a Promise
) to createStore
. The store will initially be empty (or hold the unresolved Promise object itself, depending on internal handling) until the Promise resolves.
Important Considerations:
$get
, $set
, $act
, $use
) will operate on the unresolved Promise or an initial empty state until resolution.null
) and then update it using $set
once the data is fetched.Example:
import { createStore } from "@ibnlanre/portal";
interface UserData {
id: number;
name: string;
email: string;
}
async function fetchInitialData(): Promise<UserData> {
// Simulate API call
return new Promise((resolve) =>
setTimeout(
() => resolve({ id: 1, name: "Lyn", email: "lyn@example.com" }),
500
)
);
}
const userStore = await createStore(fetchInitialData());
// At this point, the promise has resolved, and the store is initialized.
const userData = userStore.$get();
console.log(userData); // { id: 1, name: "Lyn", email: "lyn@example.com" }
// userData is a single object. userStore.id does not exist as a sub-store.
// To update, you'd set the whole object:
userStore.$set({ id: 2, name: "Alex", email: "alex@example.com" });
If you need a nested store structure from asynchronously loaded data, initialize the store with a placeholder structure (or null
) and then update it using $set
once the data is fetched. This allows the composite store structure to be established correctly.
import { createStore } from "@ibnlanre/portal";
interface AppData {
user: { name: string; role: string } | null;
settings: { theme: string } | null;
loading: boolean;
}
const appDataStore = createStore<AppData>({
user: null,
settings: null,
loading: true,
});
async function loadAppData() {
try {
// const fetchedData = await fetchActualDataFromAPI();
const fetchedData = {
// Example fetched data
user: { name: "Sam", role: "admin" },
settings: { theme: "dark" },
};
appDataStore.$set({ ...fetchedData, loading: false });
// Now appDataStore.user.name.$get() would work.
console.log(appDataStore.user.name.$get()); // "Sam"
} catch (error) {
console.error("Failed to load app data:", error);
appDataStore.$set({ user: null, settings: null, loading: false }); // Handle error state
}
}
loadAppData();
@ibnlanre/portal
handles objects with circular references safely during store creation and operations. This is particularly useful for complex data structures, such as graphs or when working with certain browser objects (after normalization).
Example:
import { createStore } from "@ibnlanre/portal";
// Define a type for clarity
interface Node {
name: string;
connections: Node[];
metadata?: { type: string };
}
const nodeA: Node = {
name: "A",
connections: [],
metadata: { type: "root" },
};
const nodeB: Node = {
name: "B",
connections: [],
metadata: { type: "leaf" },
};
nodeA.connections.push(nodeB); // nodeA points to nodeB
nodeB.connections.push(nodeA); // nodeB points back to nodeA (circular reference)
const graphStore = createStore({
nodes: [nodeA, nodeB], // 'nodes' is an array of Node objects
selectedNode: nodeA, // 'selectedNode' is a Node object
});
// Accessing data:
// 1. For 'selectedNode' (a direct object property, so it and its properties are stores)
console.log(graphStore.selectedNode.name.$get()); // "A"
if (graphStore.selectedNode.metadata) {
// Check if metadata exists
console.log(graphStore.selectedNode.metadata.type.$get()); // "root"
}
// 2. For 'nodes' (an array property; elements are not individual stores)
const currentNodes = graphStore.nodes.$get(); // Get the array value
// Access properties of objects within the 'currentNodes' array
console.log(currentNodes[0].name); // "A" (Accessing nodeA.name directly)
console.log(currentNodes[0].connections[0].name); // "B" (Accessing nodeA.connections[0].name which is nodeB.name)
// Demonstrating the circular reference is preserved:
console.log(currentNodes[0].connections[0].connections[0].name); // "A" (nodeA -> nodeB -> nodeA)
// Updates also work correctly:
// Update via 'selectedNode' store
graphStore.selectedNode.name.$set("Node Alpha");
console.log(graphStore.selectedNode.name.$get()); // "Node Alpha"
// The original nodeA object (referenced by selectedNode and within the nodes array) is updated
console.log(nodeA.name); // "Node Alpha"
// Verify in the array retrieved from the store
const updatedNodes = graphStore.nodes.$get();
console.log(updatedNodes[0].name); // "Node Alpha"
// If you were to update an element within the 'nodes' array, you'd do it like this:
graphStore.nodes.$set((prevNodes) => {
const newNodes = [...prevNodes];
// Example: Change name of the second node (nodeB)
if (newNodes[1]) {
newNodes[1] = { ...newNodes[1], name: "Node Beta" };
}
return newNodes;
});
// Assuming nodeB was correctly updated in the array:
const finalNodes = graphStore.nodes.$get();
if (finalNodes[1]) {
console.log(finalNodes[1].name); // Should be "Node Beta"
}
// And the original nodeB object is also updated if its reference was maintained
console.log(nodeB.name); // "Node Beta"
Warning: Circular references are supported, but be mindful of performance with very large or deeply nested graphs.
When your store’s state includes arrays, @ibnlanre/portal
treats them in a specific way:
Arrays as store properties: If an array is a direct property of your initial state object (e.g., items: [1, 2, 3]
in createStore({ items: [...] })
), then store.items
becomes a store instance that manages this array. You can use $get()
, $set()
, and $act()
on store.items
to interact with the entire array.
const store = createStore({ tags: ["typescript", "state-management"] });
const currentTags = store.tags.$get(); // ['typescript', 'state-management']
store.tags.$set(["javascript", "react"]); // Replaces the array
Elements within arrays are not individual stores: Objects or other values inside an array are treated as plain data. They are not automatically wrapped as individual store instances. This means you cannot call store methods like $get()
or $set()
directly on an array element, even if that element is an object.
const store = createStore({
users: [
{ id: 1, name: "Alice" },
{ id: 2, name: "Bob" },
],
});
// Correct: Get the array, then access elements
const usersArray = store.users.$get();
const firstUserName = usersArray[0].name; // "Alice"
// Incorrect: Attempting to treat an array element as a store
const firstUserStore = store.users[0]; // This is not how to access it
const name = store.users[0].name.$get(); // This will cause an error
Updating arrays:
$set()
on the array’s store property:
const listStore = createStore({ items: [1, 2, 3] });
listStore.items.$set([4, 5, 6]);
console.log(listStore.items.$get()); // Output: [4, 5, 6]
To modify the array (e.g., add, remove, or update elements), use a functional update with $set()
on the array’s store property. This ensures immutability by creating a new array.
const userListStore = createStore({
users: [{ id: 1, name: "Alex", details: { age: 30 } }],
});
// Add a new user
userListStore.users.$set((currentUsers) => [
...currentUsers,
{ id: 2, name: "Jordan", details: { age: 25 } },
]);
// Update an existing user's name
userListStore.users.$set((currentUsers) =>
currentUsers.map((user) =>
user.id === 1 ? { ...user, name: "Alexandra" } : user
)
);
// To update a nested property within an object in an array:
userListStore.users.$set((currentUsers) =>
currentUsers.map((user) =>
user.id === 1
? { ...user, details: { ...user.details, age: 31 } }
: user
)
);
Arrays of primitive values: These are handled straightforwardly. The array itself is the store property.
const numberListStore = createStore({ ids: [101, 102, 103] });
numberListStore.ids.$set((prevIds) => [...prevIds, 104]);
This behavior ensures that arrays are managed predictably as collections, while direct object properties of a store are augmented for more granular control. If you require each item in a collection to have full store capabilities, consider structuring your state as an object mapping IDs to individual stores, rather than an array of items. For example:
const itemStores = createStore({
item_1: { name: "Item A", stock: 10 },
item_2: { name: "Item B", stock: 5 },
});
// Now itemStores.item_1 is a store, itemStores.item_1.name is a store, etc.
InferType
The InferType
utility type allows you to extract TypeScript types from your Portal stores. This is especially useful when you need to work with the underlying state type in other parts of your application, such as API calls, form validation, or when passing state to other components.
Syntax:
InferType<Store, Path?>;
Parameters:
Store
: The store from which to infer the type (must extend PrimitiveStore<any>
)Path
(optional): A path within the store’s state to extract a specific nested typeReturns: The TypeScript type of the store’s state, or the type at the specified path
Examples:
Infer the complete state type:
import { createStore, InferType } from "@ibnlanre/portal";
const userStore = createStore({
age: 30,
name: "Alice",
preferences: {
notifications: true,
theme: "dark",
},
});
// Infer the complete state type
type UserState = InferType<typeof userStore>;
function saveUserToAPI(user: UserState) {
return fetch("/api/users", {
body: JSON.stringify(user),
method: "POST",
});
}
// Get the current state with correct typing
const currentUser = userStore.$get(); // Type is automatically UserState
saveUserToAPI(currentUser);
Infer specific nested types:
import { createStore, InferType } from "@ibnlanre/portal";
const appStore = createStore({
data: {
comments: [],
posts: [],
},
user: {
profile: {
email: "bob@example.com",
name: "Bob",
},
settings: {
language: "en",
theme: "light",
},
},
});
type AppData = InferType<typeof appStore, "data">;
// UserProfile is: { name: string; email: string; }
// Extract specific nested types
type UserProfile = InferType<typeof appStore, "user.profile">;
// UserSettings is: { theme: string; language: string; }
type UserSettings = InferType<typeof appStore, "user.settings">;
// AppData is: { posts: any[]; comments: any[]; }
// Use inferred types for type-safe operations
function updateProfile(newProfile: Partial<UserProfile>) {
appStore.user.profile.$set((current) => ({ ...current, ...newProfile }));
}
function updateSettings(settings: UserSettings) {
appStore.user.settings.$set(settings);
}
Use with primitive stores:
import { createStore, InferType } from "@ibnlanre/portal";
const countStore = createStore(0);
const nameStore = createStore("Hello");
const itemsStore = createStore<string[]>([]);
type CountType = InferType<typeof countStore>; // number
type ItemsType = InferType<typeof itemsStore>; // string[]
type NameType = InferType<typeof nameStore>; // string
// Use inferred types in function parameters
function processCount(value: CountType) {
console.log(`Processing count: ${value}`);
}
function processItems(items: ItemsType) {
return items.map((item) => item.toUpperCase());
}
Integration with forms and validation:
import { createStore, InferType } from "@ibnlanre/portal";
const formStore = createStore({
email: "",
profile: {
bio: "",
firstName: "",
lastName: "",
},
username: "",
});
type FormData = InferType<typeof formStore>;
type ProfileData = InferType<typeof formStore, "profile">;
async function submitForm(formData: FormData) {
const response = await fetch("/api/register", {
body: JSON.stringify(formData),
headers: { "Content-Type": "application/json" },
method: "POST",
});
return response.json();
}
function validateForm(data: FormData): boolean {
return (
data.username.length > 0 &&
data.email.includes("@") &&
data.profile.firstName.length > 0
);
}
const currentFormData = formStore.$get();
if (validateForm(currentFormData)) {
await submitForm(currentFormData);
}
The InferType
utility ensures type safety when working with store data outside of the reactive context, making it easier to integrate Portal stores with other parts of your TypeScript application.
@ibnlanre/portal
allows you to persist store state across sessions using storage adapters. These adapters provide getState
and setState
functions that you integrate with your store.
Use createLocalStorageAdapter
or createSessionStorageAdapter
to persist in the browser’s Local Storage or Session Storage.
Syntax:
createLocalStorageAdapter<State>(key: string, options?: StorageAdapterOptions<State>)
createSessionStorageAdapter<State>(key: string, options?: StorageAdapterOptions<State>)
Parameters:
key: string
: Required. A unique string identifying this store’s data in web storage.options?: StorageAdapterOptions<State>
: Optional configuration object with:
stringify?: (state: State) => string
: Function to serialize the state before saving. Defaults to JSON.stringify
.parse?: (storedString: string) => State
: Function to deserialize the state after loading. Defaults to JSON.parse
.Return Value:
Both adapters return a tuple: [getStateFunction, setStateFunction]
.
getStateFunction(): S | null
: Retrieves the state from storage. Returns null
if no state is found for the key.setStateFunction(newState: S): void
: Saves the new state to storage.createLocalStorageAdapter
Persists state in localStorage
. Data remains until explicitly cleared or removed by the user/browser.
Example:
import { createStore, createLocalStorageAdapter } from "@ibnlanre/portal";
const localStorageAdapter = createLocalStorageAdapter<number>("app-counter", {
// Example with custom serialization (e.g., simple obfuscation)
// stringify: (state) => btoa(JSON.stringify(state)),
// parse: (storedString) => JSON.parse(atob(storedString)),
});
const [getStoredCounter, setStoredCounter] = localStorageAdapter;
// Load persisted state or use a default if nothing is stored
const initialCounterState = getStoredCounter(0); // Default to 0 if null
const persistentCounterStore = createStore(initialCounterState);
// Subscribe to store changes to save them to Local Storage
persistentCounterStore.$act((newState) => {
setStoredCounter(newState);
}, false); // `false` prevents saving immediately on setup, only on actual changes
// Example usage:
persistentCounterStore.$set(10); // State is now 10 and saved to Local Storage
persistentCounterStore.$set((prev) => prev + 5); // State is 15 and saved
createSessionStorageAdapter
Persists state in sessionStorage
. Data remains for the duration of the page session (until the browser tab is closed).
Example:
import { createStore, createSessionStorageAdapter } from "@ibnlanre/portal";
const [getStoredSessionData, setStoredSessionData] =
createSessionStorageAdapter<{
guestId: string | null;
lastPage: string;
}>("userSessionData");
const initialSessionData = getStoredSessionData({
guestId: null,
lastPage: "/",
});
const sessionDataStore = createStore(initialSessionData);
sessionDataStore.$act(setStoredSessionData, false);
// Example:
sessionDataStore.$set({ guestId: "guest-123", lastPage: "/products" });
// This data will be cleared when the tab is closed.
Use createCookieStorageAdapter
for persisting state in browser cookies.
Syntax:
createCookieStorageAdapter<State>(key: string, options?: CookieStorageAdapterOptions<State>)
Parameters:
key: string
: Required. The name of the cookie.options?: CookieStorageAdapterOptions<State>
: Optional configuration object with:
secret?: string
: Secret string for signing and verifying cookies. If provided, cookies are tamper-proofed.stringify?: (state: State) => string
: Function to serialize the state. Defaults to JSON.stringify
.parse?: (storedString: string) => State
: Function to deserialize the state. Defaults to JSON.parse
.path
, domain
, secure
, sameSite
, maxAge
, etc.)path?: string
: Cookie path (e.g., /
).domain?: string
: Cookie domain.maxAge?: number
: Max age in seconds (e.g., 3600 * 24 * 7
for 7 days).expires?: Date
: Expiration date.secure?: boolean
: If true
, cookie is only sent over HTTPS.sameSite?: 'strict' | 'lax' | 'none'
: SameSite attribute.stringify?
/ parse?
: Same as web storage adapters.Return Value:
[getCookieStateFunction, setCookieStateFunction]
getCookieStateFunction(): S | null
: Retrieves and unsigns (if secret
provided) the cookie value.setCookieStateFunction(newState: S, newCookieOptions?: CookieOptions): void
: Signs (if secret
provided) and sets the cookie. newCookieOptions
can override initial options for this specific set.Example:
import { createStore, createCookieStorageAdapter } from "@ibnlanre/portal";
const cookieAdapter = createCookieStorageAdapter<{
theme: "light" | "dark";
notifications: boolean;
}>("app-preferences", {
secret: "your-very-strong-secret-key-for-signing", // Recommended for security
path: "/",
secure: true,
sameSite: "lax",
maxAge: 3600 * 24 * 30, // 30 days
});
const [getCookiePreferences, setCookiePreferences] = cookieAdapter;
const initialPrefs = getCookiePreferences({
theme: "light",
notifications: true,
});
const prefsStore = createStore(initialPrefs);
prefsStore.$act((newPrefs) => {
setCookiePrefs(newPrefs);
// Example: Update maxAge on a specific change
if (newPrefs.notifications === false) {
setCookiePrefs(newPrefs, { maxAge: 3600 * 24 }); // Shorter expiry if notifications off
}
}, false);
prefsStore.$set({ theme: "dark" }); // State saved to a signed cookie
Signed cookies: If you provide a secret
, cookies are automatically signed before being set and verified when retrieved. This helps protect against client-side tampering.
For custom storage mechanisms (e.g., IndexedDB, a remote API, chrome.storage
), use createBrowserStorageAdapter
.
Syntax:
createBrowserStorageAdapter<State, StoredState>(
key: string,
options: BrowserStorageAdapterOptions<State, StoredState>
): [
getStorageState: GetBrowserStorage<State>,
setStorageState: SetBrowserStorage<State>,
]
Parameters:
key: string
: Required. A key for your custom storage.options: BrowserStorageAdapterOptions<State>
: Required configuration object with:
getItem: (key: string) => string | null
: Function to retrieve an item.setItem: (key: string, value: string) => void
: Function to save an item.removeItem: (key: string) => void
: Function to remove an item.stringify?: (state: State) => string
: Function to serialize the state. Defaults to JSON.stringify
.parse?: (storedString: string) => State
: Function to deserialize the state. Defaults to JSON.parse
.Return Value:
[getStorageState, setStorageState]
getStorageState(fallback?: State): State | undefined
parse
function.setStorageState(value?: State): void
stringify
function.Example (using a simple in-memory object as custom storage):
import { createStore, createBrowserStorageAdapter } from "@ibnlanre/portal";
const customStorage = {
data: {} as Record<string, string>,
getItem(key: string) {
return this.data[key];
},
removeItem(key: string) {
delete this.data[key];
},
setItem(key: string, value: string) {
this.data[key] = value;
},
};
const [getCustomState, setCustomState] = createBrowserStorageAdapter<{
lastSync: null | string;
}>("custom-key", customStorage);
const initialCustomData = getCustomState({ lastSync: null });
const customDataStore = createStore(initialCustomData);
customDataStore.$act(setCustomState, false);
customDataStore.$set({ lastSync: new Date().toISOString() });
The createAsyncBrowserStorageAdapter
is a more flexible version of createBrowserStorageAdapter
. It allows for asynchronous transformations of your state, which is useful when you need to perform operations like encryption, compression, or other async tasks before storing or retrieving the state.
The adapter provides two functions: one for getting the state from storage and another for setting the state to storage. Both functions can handle asynchronous operations, allowing you to work with data that requires processing before being used in your application.
Syntax:
createAsyncBrowserStorageAdapter<State, StoredState = State>(
key: string,
options: AsyncBrowserStorageAdapterOptions<State, StoredState>
): [
getStorageState: AsyncGetBrowserStorage<State>,
setStorageState: AsyncSetBrowserStorage<State>,
]
Parameters:
key: string
: Required. A key for your custom storage.options: BrowserStorageAdapterOptions<State>
: Required configuration object with:
getItem: (key: string) => Promise<string | null> | string | null
: Function to retrieve an item.setItem: (key: string, value: string) => Promise<void> | void
: Function to save an item.removeItem: (key: string) => Promise<void> | void
: Function to remove an item.beforeUsage?
: A function that transforms the data from storage before it’s used in your application.beforeStorage?
: A function that transforms the data to be stored.Return Value:
[getStorageState, setStorageState]
getStorageState(fallback?: State): Promise<State | undefined>
beforeUsage
function.setStorageState(value?: State): Promise<void>
beforeStorage
function.Example:
Let’s create an adapter that simulates async encryption and decryption.
import { createAsyncBrowserStorageAdapter } from "@ibnlanre/portal";
const [getEncryptedState, setEncryptedState] = createAsyncBrowserStorageAdapter<
{ sensitive: string },
string
>("encrypted", {
getItem(key) {
return localStorage.getItem(key);
},
removeItem(key) {
return localStorage.removeItem(key);
},
setItem(key, value) {
return localStorage.setItem(key, value);
},
beforeStorage(data) {
return btoa(JSON.stringify(data)); // Encrypt before storing
},
beforeUsage(data) {
return JSON.parse(atob(data)); // Decrypt when retrieving
},
});
// Now, you can use these functions to persist a store
const result = await getEncryptedState({ sensitive: "data" });
// When the store is initialized, the data will be decrypted.
const store = createStore(result);
// When you set the state, it will be encrypted before being stored.
store.$act(setEncryptedState, false);
Beyond the createCookieStorageAdapter
, @ibnlanre/portal
also exposes a cookieStorage
module. This module provides a collection of utility functions for direct, granular manipulation of browser cookies. You might use these functions if you need to interact with cookies outside the context of a store or require more fine-grained control than the adapter offers.
These utilities are particularly helpful for tasks like signing/unsigning cookie values for security, directly reading or writing specific cookies, or managing cookie properties with precision.
Access the module:
To use these utilities, import cookieStorage
:
import { cookieStorage } from "@ibnlanre/portal";
The cookieStorage
object provides the following functions and properties:
sign()
Signs a string value using a secret key. This is useful for creating tamper-proof cookie values.
value: string
: The string to sign.secret: string
: The secret key for signing.string
- The signed string.Example:
const originalValue = "user-session-data";
const secretKey = "your-super-secret-key";
const signedValue = cookieStorage.sign(originalValue, secretKey);
// signedValue might look like "user-session-data.asdfjklsemf..."
unsign()
Verifies and unsigns a previously signed string using the corresponding secret key.
signedValue: string
: The signed string to unsign.secret: string
: The secret key used for signing.string | false
- The original string if the signature is valid, or false
if tampering is detected or the secret is incorrect.Example:
const potentiallyTamperedValue = "user-session-data.asdfjklsemf...";
const secretKey = "your-super-secret-key";
const originalValue = cookieStorage.unsign(
potentiallyTamperedValue,
secretKey
);
if (originalValue === false) {
console.error("Cookie signature is invalid!");
} else {
console.log("Original value:", originalValue);
}
getItem()
Retrieves the value of a cookie by its name (key).
key: string
: The name of the cookie.string | null
- The cookie’s value, or null
if the cookie is not found.Example:
const themePreference = cookieStorage.getItem("userTheme");
if (themePreference) {
console.log("User theme:", themePreference);
}
setItem()
Sets or updates a cookie’s value. You can also provide cookie options.
key: string
: The name of the cookie.value: string
: The value to store in the cookie.options?: CookieOptions
: Optional. An object specifying cookie attributes (e.g., path
, expires
, secure
). Refer to the CookieOptions
type definition for details.void
Example:
cookieStorage.setItem("userToken", "abc123xyz789", {
secure: true,
path: "/",
maxAge: 3600 * 24, // 1 day in seconds
});
removeItem()
Removes a cookie by its name.
key: string
: The name of the cookie to remove.options?: CookieOptions
: Optional. Cookie options (like path
and domain
) that must match the options used when the cookie was set for successful removal.void
Example:
cookieStorage.removeItem("userToken", { path: "/" });
clear()
Attempts to clear all cookies accessible to the current document’s path and domain by setting their expiration date to the past. Note that this might not remove cookies set with specific path
or domain
attributes unless those are also iterated and cleared individually.
void
Example:
cookieStorage.clear(); // Clears cookies for the current path/domain
createKey()
Constructs a standardized cookie name string based on a set of provided options. This helps maintain consistent naming conventions for cookies across your application.
cookieFragmentDescription?: string
: A description for the cookie’s purpose (e.g., “Authentication Token”).cookiePrefix?: string
: A prefix for the cookie name (e.g., "__Host-"
). Default: ""
.cookieFragmentSizes?: number[]
: Array defining sizes for fragments if the description is segmented. Default: []
.cookieScope?: string
: The scope of the cookie (e.g., “session”, “user”). Default: ""
.cookieScopeCase?: "title" | "upper" | "lower" | "camel" | "snake" | "pascal" | "header" | "constant"
: The case formatting for the scope part. Default: "title"
.cookieService?: string
: The service associated with the cookie. Default: ""
.cookieScopeServiceConnector?: string
: Connector between scope and service. Default: "-"
.cookieScopeFragmentConnector?: string
: Connector between scope and fragment description. Default: "_"
.cookieFragmentsConnector?: string
: Connector between multiple fragments of the description. Default: ""
.cookieSuffix?: string
: A suffix for the cookie name. Default: ""
.string
- The generated cookie name.Example:
const authTokenKey = cookieStorage.createKey({
cookieFragmentDescription: "Authentication Token",
cookiePrefix: "__Secure-",
cookieScope: "userSession",
cookieScopeCase: "camel",
});
// authTokenKey might be "__Secure-userSession_AuthenticationToken"
console.log(authTokenKey);
key()
Retrieves the name (key) of a cookie at a specific index in the document’s cookie string. The order of cookies can be browser-dependent.
index: number
: The zero-based index of the cookie.string | null
- The cookie name at the specified index, or null
if the index is out of bounds.Example:
const firstCookieName = cookieStorage.key(0);
if (firstCookieName) {
console.log("Name of the first cookie:", firstCookieName);
}
length
(Property)Retrieves the total number of cookies accessible to the current document.
number
Example:
const numberOfCookies = cookieStorage.length;
console.log(`There are ${numberOfCookies} cookies.`);
@ibnlanre/portal
is designed for performance, but here are some tips for optimal usage in complex applications:
Use selectors for reactive derived data: When you need derived state that should update when dependencies change, use selectors with $use()
that depend on the actual store state, not external variables.
// ✅ Correct: Selector depends on store state - updates reactively
const [userItems] = appStore.$use((state) =>
state.items.filter((item) => item.ownedBy === state.selectedUserId)
);
// ❌ Incorrect: External variable captured in closure - won't update
const [userItems] = itemsStore.$use(
(items) => items.filter((item) => item.ownedBy === selectedUserId) // selectedUserId is external
);
Leverage dependency arrays for expensive computations: When using selectors with $use()
, provide a dependency array for expensive computations to prevent unnecessary recalculations.
// Expensive calculation with proper dependencies
const [processedData] = store.$use(
(state) => expensiveDataProcessing(state.rawData, complexConfig),
[complexConfig] // Only re-run if complexConfig changes
);
Choose the right approach for derived state: Use different patterns based on your reactivity needs:
// For reactive derived state (updates components automatically)
const [totalPrice] = cartStore.$use((cart) =>
cart.items.reduce((sum, item) => sum + item.price * item.quantity, 0)
);
// For one-time calculations (doesn't subscribe to changes)
const handleCheckout = () => {
const total = cartStore.$get((cart) =>
cart.items.reduce((sum, item) => sum + item.price * item.quantity, 0)
);
processPayment(total);
};
Avoid common reactivity pitfalls:
useMemo
with incomplete dependencies: If you use React’s useMemo
for derived state, ensure all store data is included in the dependency array.Structure state for optimal updates: Organize your state to minimize unnecessary re-renders:
// ✅ Good: Related data grouped together
const uiStore = createStore({
modals: { loginVisible: false, cartVisible: false },
notifications: { count: 0, items: [] },
theme: "dark",
});
// ❌ Less optimal: Separate stores for closely related UI state
const loginModalStore = createStore(false);
const cartModalStore = createStore(false);
const notificationStore = createStore({ count: 0, items: [] });
Keep components simple: Components should focus on rendering UI and handling user interactions. Move complex logic or data fetching to actions or hooks.
Use granular subscriptions: Subscribe only to the specific parts of state your component needs:
// ✅ Subscribe only to theme
const [theme] = uiStore.theme.$use();
// ❌ Subscribe to entire UI store when only theme is needed
const [uiState] = uiStore.$use();
const theme = uiState.theme;
Batch related updates: When making multiple related changes, batch them to prevent intermediate re-renders. This is especially important in React, where each state change can trigger a re-render:
// ✅ Single update for related changes
userStore.$set((prevUser) => ({
...prevUser,
name: newName,
email: newEmail,
lastUpdated: Date.now(),
}));
// ❌ Multiple separate updates trigger multiple re-renders
userStore.name.$set(newName);
userStore.email.$set(newEmail);
userStore.lastUpdated.$set(Date.now());
Profile and measure: Use React DevTools Profiler and browser performance tools to identify actual performance bottlenecks rather than premature optimization.
While @ibnlanre/portal
is versatile, it’s important to be aware of its limitations:
undefined
(in some parts of objects when using JSON.stringify
), or complex class instances might not serialize/deserialize correctly by default. Customize stringify
and parse
options in adapters for complex scenarios. Functions within stores (actions) are not persisted.const store = createStore({
name: "Alice",
lastLogin: new Date(), // Date objects need custom serialization
preferences: {
theme: "dark",
notifications: true,
},
});
const [getState, setState] = createLocalStorageAdapter("user-store", {
stringify: (state) =>
JSON.stringify({
...state,
lastLogin: state.lastLogin.toISOString(), // Convert Date to string
}),
parse: (storedString) => {
const parsed = JSON.parse(storedString);
return {
...parsed,
lastLogin: new Date(parsed.lastLogin), // Convert string back to Date
};
},
});
$get()
directly (without using $set()
), the store will not detect the change, and subscribers (including React components using $use()
) will not update. Always use $set()
or the updater function from $use()
to modify state.// ❌ Direct mutation - won't trigger reactivity
const user = userStore.$get();
user.name = "New Name"; // No reactivity triggered
// ✅ Correct way - triggers reactivity
userStore.$set((prev) => ({ ...prev, name: "New Name" }));
Promise resolution in createStore
: When createStore
is initialized with a Promise, the resolved value is treated as a single entity. If the Promise resolves to an object, this object becomes the state of a primitive-like store, not a composite store with automatically created nested properties. To achieve a nested structure from async data, initialize the store with a placeholder and use $set
after data fetching.
// ❌ This creates a primitive-like store with the resolved object as its value
const userStore = createStore(fetchUserData()); // fetchUserData returns Promise<{ name: string; age: number; }>
// ✅ This creates a composite store with nested properties
const userStore = createStore({ name: "", age: 0 });
fetchUserData().then((data) => userStore.$set(data));
To make the most of @ibnlanre/portal
, consider these best practices:
userStore
, productStore
, settingsStore
).modalStore
, notificationStore
) if it helps with clarity.$set()
or the updater from $use()
to change state. Avoid direct mutations.const cartStore = createStore({ items: [{ price: 10, quantity: 2 }] });
const totalCost = cartStore.$get((state) =>
state.items.reduce((sum, item) => sum + item.price * item.quantity, 0)
);
localStorage
: For persistent user preferences or data that should survive browser restarts.sessionStorage
: For temporary data related to a single session (e.g., form data, current tab state).cookieStorage
: For small pieces of data that need to be sent with HTTP requests or shared across subdomains, or when signed/secure cookies are needed.userStore
, profileSettingsStore
).Contributions are welcome! We appreciate your help in making @ibnlanre/portal
better.
You can contribute by:
Please read our CONTRIBUTING.md file for detailed guidelines on how to contribute, including coding standards, testing requirements, and the pull request process.
If you need help using @ibnlanre/portal
, here are the resources available to you:
Documentation:
Community Support:
Report Issues: If you can’t find a solution, open a new issue on GitHub with:
@ibnlanre/portal
This project is licensed under the BSD-3-Clause License. Copyright (c) 2025, ibnlanre.