jotai breaking changes

3.0.0

15 breaking changes, first published September 8, 2026.

• Removed
  Jotai v3 requires Node.js 22.12.0 or later. Code running on older Node.js versions must upgrade Node.js before moving to v3. github.com
• Removed
  Importing internal files of the package directly no longer works. Import only from the public entry points. github.com
• Removed
  Jotai v3 requires React 18 or later. Apps on React 17 must upgrade React first. github.com
• Removed
  Only the ESM build is published now. Code that loads Jotai from CJS must use require() on Node.js versions that support it, or bundle the ESM build. github.com
• Removed atomFamily
  Install jotai-family and import atomFamily from it instead of jotai/utils. github.com
• Removed jotai.babel
  Install jotai-babel and reference its plugins in the Babel config instead of jotai/babel. github.com
• Removed loadable
  Use unwrap instead, or implement the previous behavior in your own code. github.com
• Removed setSelf
  No direct replacement exists. Use onMount or jotai-effect depending on the use case. github.com
• Removed useAtom
  Create a custom hook that delays the update with setTimeout instead. github.com
• Removed useAtomValue
  Create a custom hook that delays the update with setTimeout instead. github.com

And 5 more in this version.

Check your code

These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.