Skip to main content

Multi-Tab State Sync Made Easy: Introducing useSharedState in react-hook-lab!

Multi-Tab State Sync Made Easy: Introducing useSharedState in react-hook-lab!

If you've ever had to build a web application where users open multiple tabs, you know the struggle of keeping state synchronized. Whether it's a shopping cart, user preferences, or live dashboard configurations, manual synchronization using localStorage events or WebSockets can quickly turn into a boilerplate-heavy headache.

Today, I'm thrilled to share a major feature update to react-hook-lab: the introduction of the useSharedState hook! This release also includes some source-tree spring cleaning to ensure a lighter, cleaner library.

What's New: Multi-Tab State Synchronization 🔄

The star of this release is the new useSharedState hook. This hook allows you to seamlessly share and synchronize state across multiple browser tabs or windows in real-time, completely out of the box.

Under the hood, useSharedState is powered by a robust, custom-engineered sync engine:

  • BroadcastChannel Transport: It utilizes the native BroadcastChannel API to instantly broadcast state updates across same-origin tabs.
  • Conflict Resolution: If two tabs update state at almost the same time, the engine automatically resolves conflicts using logical versioning and unique tab identifiers.
  • Reactive Event Bus: An internal event bus coordinates local state changes with React's rendering lifecycle.
  • Snapshot Management: It integrates smoothly with modern React state mechanics, ensuring zero tearing and optimal re-rendering.

How to Use It

Using useSharedState is designed to feel exactly like using React's native useState. Just provide a unique sync key and an initial value:

import React from 'react';
import { useSharedState } from 'react-hook-lab';

function ThemeSelector() {
  // State is automatically synchronized across all open tabs!
  const [theme, setTheme] = useSharedState('app-theme', 'light');

  return (
    <div>
      <p>Current Theme: {theme}</p>
      <button onClick={() => setTheme('light')}>Light Mode</button>
      <button onClick={() => setTheme('dark')}>Dark Mode</button>
    </div>
  );
}

Library Housekeeping 🧹

As part of our commitment to keeping the repository clean and maintainable, we have also done some housekeeping. We removed pre-compiled build files (index.js and index.d.ts) from the root of the source tree. This ensures that our version control remains focused strictly on the TypeScript source code, preventing build artifacts from cluttering up pull requests.

Resources & Links

Labels:

Comments

Post a Comment

Popular posts from this blog

Supercharge Your React Apps: Declarative Client Downloads and Desktop Notifications

Enhancing web application interactivity often involves direct interaction with native browser capabilities. Common tasks like exporting JSON reports or sending native OS alerts usually force developers to craft imperative DOM manipulations, handle dynamic Blob object URLs, or coordinate web browser permissions. The latest release of react-hook-lab solves these challenges by introducing two production-ready hooks: useDownload and useNotifications . 1. Effortless Client Data Exports with useDownload The new useDownload hook simplifies client-side file downloading. It accepts plain text strings, JavaScript objects (auto-converted to JSON), Blobs, or remote URLs. It tracks download statuses ( idle , downloading , success , error ) and automatically cleans up object URLs to prevent browser memory leaks. Example: Exporting Data with useDownload import React from "react"; import { useDownload } from "react-hook-lab"; export function DataExporter() { const { ...
Post a Comment
Read more

How We Built a Performance-Safe Deep Clone Hook for React Developers

When managing complex state trees in React, developers frequently encounter the need to duplicate objects to avoid direct mutation bugs. However, traditional copying methods either fall short on complex data types or destroy rendering performance. To solve this, the latest update to react-hook-lab introduces a robust deep cloning solution built specifically for the React paradigm. The Problem with Traditional Deep Cloning Most developers rely on JSON.parse(JSON.stringify(obj)) for quick copies. Unfortunately, this method breaks on circular references, strips prototype chains, and ignores custom types like Map , Set , or Date . On the other hand, importing heavy libraries just for object copying impacts bundle size. Crucially, cloning inside a React component on every render disrupts reference equality, which can lead to disastrous infinite render loops. The Solution: A Optimized Hook & Utility To eliminate these issues, we designed a cloning algorithm that is fast, secure, ...
Post a Comment
Read more

Stop Guessing: Diagnosing React Re-Renders with the New useRenderReason Hook

Stop Guessing: Diagnosing React Re-Renders with the New useRenderReason Hook React developers have a love-hate relationship with re-renders. When a UI gets sluggish, tracking down exactly which prop, hook, or state change triggered a component to update can feel like looking for a needle in a haystack. Sure, you can write temporary useEffect blocks or pull up complex browser profilers. But what if your codebase could tell you exactly why a component re-rendered in plain English, directly in your console? To make performance optimization straightforward and stress-free, we are excited to introduce a powerful new debugging utility to the react-hook-lab family: useRenderReason ! What's Changed? We have added the useRenderReason hook, a development-time diagnostic tool that hooks into your React component's lifecycle. It tracks properties or state values you pass to it, classifies every single change, and logs clear, actionable feedback to the console. Unlike trad...
Post a Comment
Read more