npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

jotai-sync-scope

v0.0.1

Published

Library for syncing Jotai atoms

Readme

The idea is to sync two Jotai atoms by basically making writing to synced atom to write to original atom.

Definitions

  • source atom - atom that is declared/used higher in React tree
  • target atom - atom that should be synced with source atom meaning that writing to it will write the same value to the source atom

Backwards should work too. Writing to source atom should change value in target atom

Rules

  • If the atom is not synced writing to it means writing to original atom
  • If the atom is target atom then writing operation writes to associated source atom
  • If the atom is source atom then writing operation writes to the atom and target atom is updated automatically because target atom is basically the reference to source atom

Usage

import { atom, useAtom } from 'jotai';
import { SyncScopeProvider } from 'jotai-sync-scope';

const sourceAtom = atom(0);
const targetAtom = atom(0);

const App = () => {
  const [state] = useAtom(sourceAtom);

  return (
    <>
      <p>Source: {state}</p>
      <Sync />
    </>
  );
};

const Sync = (props) => {
  return (
    <SyncScopeProvider atoms={[[sourceAtom, targetAtom]]}>
      <Component />
    </SyncScopeProvider>
  );
};

const Component = () => {
  const [state, setState] = useAtom(targetAtom);

  return (
    <>
      <p>Target: {state}</p>
      <button onClick={() => setState((s) => s + 1)}>+1</button>
    </>
  );
};

Use case

One of the use cases is when you have atom with array of items and you want to provide a way to consume item within scope of some components using splitAtom and hook to the item like it's global.

import { atom, useAtom, useAtomValue, atom } from 'jotai';
import { splitAtom } from 'jotai/utils';
import { SyncScopeProvider } from 'jotai-sync-scope';

const tabsAtom = atom([]);
const tabAtomsAtom = splitAtom(tabsAtom);

const App = () => {
  const tabAtoms = useAtomValue(tabAtomsAtom);

  return (
    <>
      {tabAtoms.map((atom) => (
        <SyncScopeProvider atoms={[[atom, tabAtom]]} key={atom.key}>
          <Tab />
        </SyncScopeProvider>
      ))}
    </>
  );
};

const tabAtom = atom({});

const Tab = () => {
  const [tab, setTab] = useAtom(tabAtom);

  // You can update tabAtom value as if it's global but it's actually relates to an item from tabsAtom.
};

// You can even derive some state from tabAtom and use it to access some part of it
const tabName = atom((get) => get(tabAtom).title);