v1.4.4

This fixes a fundamental bug in core, which may affect some cases with complex derived atoms.

What's Changed

• refactor(types): enable exactOptionalPropertyTypes by @dai-shi in #839
• fix(core): mount self atom before mounting dependencies by @Thisen in #818

New Contributors

• @zacjones93 made their first contribution in #824

Full Changelog: v1.4.3...v1.4.4

v1.4.3

Now, useAtomDevtools in jotai/devtools supports read-only atoms. You can only see the read-only atom values in Redux DevTools Extention (you can't change the value, like with time-traveling.)

What's Changed

• feat(devtools): read-only atom support in useAtomDevtools by @Aslemammad in #817
• fix(core): interruptable promise handling by @dai-shi in #820
• refactor(core): improve invalidated revision by @dai-shi in #821

New Contributors

• @steinybot made their first contribution in #804

Full Changelog: v1.4.2...v1.4.3

v1.4.2

Summary

v1.4.1 has a bug in atomWithStorage types in jotai/utils, which is fixed in v1.4.2.

What's Changed

• fix(utils): add missing function overload for atomWithStorage by @dai-shi in #798
• refactor(core): revert old dependencies in atom state by @dai-shi in #799
• fix(build): resolve missing babel d.ts files by @dai-shi in #800

Full Changelog: v1.4.1...v1.4.2

v1.4.1

Summary

This adds a new experimental support for React Refresh. It has some other small fixes and improvements.

What's Changed

• feat(babel): React Refresh support by @Thisen in #782
• fix(utils): improve atomWithStorage types by @dai-shi in #784
• fix(valtio): length of array didn't update (#785) by @Mingx94 in #786
• refactor(core): retain old dependencies in atom state by @dai-shi in #793

New Contributors

• @Mingx94 made their first contribution in #786

Full Changelog: v1.4.0...v1.4.1

v1.4.0

Atom types are improved (BREAKING CHANGE in types)

Previously, sync atom and async atom are not distinguishable by types. This is improved now. If you make types inferred, there would be no changes required. If you explicitly type async atoms, migration would be required.

Migration Guide

Async writable atom

Previously, when you annotate atom() to create a writable atom, it looks like this:

const atom1 = atom(0)
const atom2 = atom<number, number>(
  (get) => get(atom1), 
  async (get, set, arg) => set(atom1, arg),
)

☝️ That will be type error.

A fix would be adding the 3rd type arg:

const atom2 = atom<number, number, Promise<void>>(
  (get) => get(atom1), 
  async (get, set, arg) => set(atom1, arg),
)

But, the recommendation is not to annotate atom() types, but arg only:

const atom2 = atom(
  (get) => get(atom1), 
  async (get, set, arg: number) => set(atom1, arg),
)

Async atom (read function)

Previously, async (read) atoms are typed like this:

const atom3 = atom<number>(async (get) => get(atom1))

☝️ That will not work.

A fix would be annotate it with Promsie<Value>:

const atom3 = atom<Promise<number>>(async (get) => get(atom1))

But, the recommendation is not to annotate atom() types, but to infer types:

const atom3 = atom(async (get) => get(atom1))

Async write atoms no longer suspend (BREAKING CHANGE in behavior)

Suspending on write turns out to be a bit of trouble. We should use promises.
If you depend on this behavior, you might need to do something.

Migration Guide

Previously, an async write atom suspends (triggers Suspense fallback):

const atom1 = atom(null, async (get, set, arg) => {
  // async task
})

☝️ That will not suspend any longer.

We should instead have a loading flag.

const pendingAtom = atom(false)
const atom1 = atom(null, async (get, set, arg) => {
  set(pendingAtom, true)
  // async task
  set(pendingAtom, false) // or put in finally clause
})

---

What's Changed

• breaking(types): refine atom type and other types by @dai-shi in #713
• fix(core): no async write suspense (BREAKING CHANGE in behavior) by @dai-shi in #731
• breaking(utils): remove deprecated signature of atomWithHash by @dai-shi in #763
• fix(utils): resolve undefined observable by @dai-shi in #777

New Contributors

• @ricmello made their first contribution in #774

Full Changelog: v1.3.9...v1.4.0

v1.3.9

Summary

There was an edge-case issue with async atoms reported #751, which is fixed. Other changes are basically refactoring, but they may fix some potential bugs.

What's Changed

• fix(core): resolve infinite loop with chained async dependencies by @dai-shi in #766
• fix(query): improve atomWith(Infinite)Query with enabled by @dai-shi in #767
• fix(core): improve reading atom state by @dai-shi in #768
• fix(core): promise handling in store by @dai-shi in #769

Full Changelog: v1.3.8...v1.3.9

v1.3.8

Summary

jotai/utils

• atomWithHash takes options object for more customization
  • the old signature (serialize/deserialize functions) is deprecated and will be remove in the next version

jotai/valtio

• atomWithProxy takes options object for enable sync option

PRs

• #752 fix(valtio): Add option for atomWithProxy to be synchronous
• #758 fix(utils): atomWithHash options

v1.3.7

Summary

v1.3.4-1.3.6 accidentally requires newer node.js versions. v1.3.7 fixes it by reverting exports format.
This also fixes handling async atoms with chained dependency, which solves some cases.

PRs

• #734 refactor(utils): loadable util
• #735 refactor(core): commitAtom in store
• #747 fix(core): resume from suspense on derived atom with async atom dependency
• #748 fix(package): avoid subpath pattern in exports

v1.3.6

⚠️ Minimum Node.js requirements (for server-side usage like Next.js): v14.13.0, v12.20.0

Summary

This fixes a false positive warning in some environments reported in #709. It also comes with some refactoring for more code maintainability.

PRs

• #717 refactor(core,utils,devtools): add dev methods in store
• #719 chore(build): pin esbuild for now and replace size plugin with github action
• #727 refactor(core): interruptable promise implementation
• #730 fix(core,utils): support unknown error type
• #732 chore(build): upgrade and unpin esbuild and fix compressed size action

v1.3.5

⚠️ Minimum requirements for Node.js (for server-side usage like Next.js): v14.13.0, v12.20.0

Summary

v1.3.4 requires node >= 14 in package.json, which may cause some issues in certain envs. As we don't require it, this reverts back to node >= 12. This also adds babel preset in jotai/babel.

PRs

• #706 feat(babel): Babel preset for Jotai
• #710 refactor(utils,immer,optics): with memoizeAtom
• #716 fix(build): Switch back to Node 12