Sourcemap Explorer
Stack · npm package

jotai

👻 Primitive and flexible state management for React

latest 2.20.2· MIT· 210 versions publishedView on npm

About

👻 Primitive and flexible state management for React

reactstatemanagermanagementrecoilstore

What detecting jotai tells you about a site

jotai reveals an atomic approach to state — many small, composable atoms rather than one global store — chosen by teams that found Redux too monolithic and wanted bottom-up state with first-class React Suspense support. Its presence signals a modern, granular React architecture.

Why the exact jotai version matters

Jotai 2 changed the core store API and async-atom behaviour; the exact version tells you which atom API the code targets and whether it uses the newer store primitives.

jotai in a real-world stack

When you find jotai in a bundle, it rarely travels alone. react, and frequently @tanstack/react-query for server state alongside jotai's UI/client state.

Quick facts

Latest version2.20.2
LicenseMIT
AuthorDaishi Kato
Installnpm install jotai
Direct dependencies0
Peer dependenciesreact, @babel/core, @types/react, @babel/template

Common pairings

Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.

react@babel/core@types/react@babel/template

How Sourcemap Explorer detects jotai

jotai ships as v2.20.2, published 2026-07-14 and carries 0 direct dependencies, 4 peer dependencies (react, @babel/core, @types/react), 210 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when jotai rides inside a deployed bundle — here is how the detection works.

We catch jotai from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/jotai/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `jotai` paths live.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/jotai/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/jotai/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/jotai/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of jotai

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the jotai version a site actually ships against the ecosystem.

Major
First release
Date
v2
2.0.0
2023-01-31
v1
1.0.0
2021-06-14
v0
0.0.0
2020-08-11

Recent versions

Version
Released
2.20.2
2026-07-14
2.20.1
2026-06-11
2.20.0
2026-05-06
2.19.1
2026-04-07
2.19.0
2026-03-24
2.18.1
2026-03-09
2.18.0
2026-02-19
2.17.1
2026-02-04

jotai README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.


Jotai (light mode) Jotai (dark mode)


visit jotai.org or npm i jotai

Build Status Build Size Version Downloads Discord Shield Open Collective

Jotai scales from a simple useState replacement to an enterprise TypeScript application.

  • Minimal core API (2kb)
  • Many utilities and extensions
  • No string keys (compared to Recoil)

Examples: Demo 1 | Demo 2

First, create a primitive atom

An atom represents a piece of state. All you need is to specify an initial value, which can be primitive values like strings and numbers, objects, and arrays. You can create as many primitive atoms as you want.

import { atom } from 'jotai'

const countAtom = atom(0)
const countryAtom = atom('Japan')
const citiesAtom = atom(['Tokyo', 'Kyoto', 'Osaka'])
const mangaAtom = atom({ 'Dragon Ball': 1984, 'One Piece': 1997, Naruto: 1999 })

Use the atom in your components

It can be used like React.useState:

import { useAtom } from 'jotai'

function Counter() {
  const [count, setCount] = useAtom(countAtom)
  return (
    <h1>
      {count}
      <button onClick={() => setCount((c) => c + 1)}>one up</button>
      ...

Create derived atoms with computed values

A new read-only atom can be created from existing atoms by passing a read function as the first argument. get allows you to fetch the contextual value of any atom.

const doubledCountAtom = atom((get) => get(countAtom) * 2)

function DoubleCounter() {
  const [doubledCount] = useAtom(doubledCountAtom)
  return <h2>{doubledCount}</h2>
}

Creating an atom from multiple atoms

You can combine multiple atoms to create a derived atom.

const count1 = atom(1)
const count2 = atom(2)
const count3 = atom(3)

const sum = atom((get) => get(count1) + get(count2) + get(count3))

Or if you like fp patterns ...

const atoms = [count1, count2, count3, ...otherAtoms]
const sum = atom((get) => atoms.map(get).reduce((acc, count) => acc + count))

Derived async atoms needs suspense

You can make the read function an async function too.

const urlAtom = atom('https://json.host.com')
const fetchUrlAtom = atom(async (get) => {
  const response = await fetch(get(urlAtom))
  return await response.json()
})

function Status() {
  // Re-renders the component after urlAtom is changed and the async function above concludes
  const [json] = useAtom(fetchUrlAtom)
  ...

You can create a writable derived atom

Specify a write function at the second argument. get will return the current value of an atom. set will update the value of an atom.

const decrementCountAtom = atom(
  (get) => get(countAtom),
  (get, set, _arg) => set(countAtom, get(countAtom) - 1)
)

function Counter() {
  const [count, decrement] = useAtom(decrementCountAtom)
  return (
    <h1>
      {count}
      <button onClick={decrement}>Decrease</button>
      ...

Write only derived atoms

Just do not define a read function.

const multiplyCountAtom = atom(null, (get, set, by) =>
  set(countAtom, get(countAtom) * by),
)

function Controls() {
  const [, multiply] = useAtom(multiplyCountAtom)
  return <button onClick={() => multiply(3)}>triple</button>
}

Async actions

Just make the write function an async function and call set when you're ready.

const fetchCountAtom = atom(
  (get) => get(countAtom),
  async (_get, set, url) => {
    const response = await fetch(url)
    set(countAtom, (await response.json()).count)
  }
)

function Controls() {
  const [count, compute] = useAtom(fetchCountAtom)
  return (
    <button onClick={() => compute('http://count.host.com')}>compute</button>
    ...

Note about functional programming

Jotai's fluid interface is no accident — atoms are monads, just like promises! Monads are an established pattern for modular, pure, robust and understandable code which is optimized for change. Read more about Jotai and monads.

Links

FAQ

What is jotai used for?

👻 Primitive and flexible state management for React

How can I tell if a website is using jotai?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `jotai` from two complementary signals: `node_modules/jotai/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

How do I find out which version of jotai a website is running?

Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `jotai/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/jotai/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 2.20.2, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.

What is the latest version of jotai?

2.20.2, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Is jotai actively maintained?

Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-14. Source code: https://github.com/pmndrs/jotai.

Where can I read more?

Project homepage: https://github.com/pmndrs/jotai. Source code: https://github.com/pmndrs/jotai. Published on npm: https://www.npmjs.com/package/jotai. Licensed as MIT.

Keep reading on Sourcemap Explorer

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for jotai and report the precise version (the registry's latest is v2.20.2, published 2026-07-14; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome