chore(deps): bump jotai-effect from 0.6.0 to 2.1.3

[dependabot]

Bumps jotai-effect from 0.6.0 to 2.1.3.

Release notes

Sourced from jotai-effect's releases.

v2.0.4

What's Changed

• fix: withAtomEffect infinite loop with atoms in atom circular dependency by @​dmaskasky in jotaijs/jotai-effect#68

Full Changelog: jotaijs/jotai-effect@v2.0.3...v2.0.4

v2.0.0

We’re excited to announce the release of jotai-effect v2, which brings a single but significant change to the core API: atomEffect now runs synchronously whenever it mounts or its dependencies change. This update improves consistency, helps avoid race conditions, and keeps related state changes in sync.

---

What’s New?

Synchronous atomEffect

• In v1, atomEffect would run asynchronously in the next microtask.
• In v2, atomEffect runs synchronously on mount and whenever the dependencies it uses have changed.
• Batching is still supported when you update multiple dependencies in a single writable atom. The effect runs only after that writable atom has finished all its updates, preventing partial updates or intermediate states.

Example:

const syncEffect = atomEffect((get, set) => {
  get(someAtom)
  set(anotherAtom)
})
const store = createStore()
store.set(someAtom, (v) => v + 1)
// The effect above runs immediately, so anotherAtom is updated in the same microtask
console.log(store.get(anotherAtom)) // Updated by atomEffect synchronously

When someAtom is updated, the effect runs immediately, updating anotherAtom in the same turn. If you update multiple atoms in the same writable atom, these changes are batched together, and atomEffect runs after those updates complete.

---

Migration Guide

For most users, no change is required. If you depended on the old microtask delay or cross-atom batching, read on.

1. Adding back the microtask delay

If your logic explicitly relied on atomEffect running in a separate microtask, you can reintroduce the delay yourself:

Before (v1)

const effect = atomEffect((get, set) => {
  console.log('effect')
</tr></table> 

... (truncated)

Commits

• 009dc39 update version to v2.1.3
• 6f256e2 fix: export Effect to resolve ts(2742) in some project setups (#73)
• 3c05289 drop atom.unstable_is usage (#76)
• e5726d7 add setup script for jotai
• e87975d refactor: support jotai 2.14.0 (#74)
• c77018f update version to 2.1.0
• 74e7cd8 Deterministic withAtomEffect ordering (#72)
• b781d87 support local jotai repo
• 20545ee Configurable debug label (#69)
• eecae3e update version to 2.0.4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cloudflare-workers-and-pages]

Deploying algokit-lora with    Cloudflare Pages

Latest commit:	7a52246
Status:	🚫  Build failed.

View logs