chore(deps): bump jotai from 1.6.1 to 1.7.0 in /web

[dependabot[bot]]

Bumps jotai from 1.6.1 to 1.7.0.

Release notes

Sourced from jotai's releases.

v1.7.0

Prior to this version, Provider catches all atoms for useDebugValue in development mode for React DevTools. One issue is that you can’t disable this behavior. The other limitation is this doesn’t work with provider-less mode. To this end, we expose a new hook useAtomsDebugValue and remove the feature from Provider. Migration is required if you are using Provider and React DevTools to see atom values in development mode.

Migration Guide

Previously, if you use <Provider>, useDebugValue is automatically used in the dev mode and you can never disable it.

import { Provider } from 'jotai'
const Root = () => (
<Provider>
<App />
</Provider>
}

Now, to get the same behavior, you need to use the useAtomsDebugValue explicitly.

import { Provider } from 'jotai'
import { useAtomsDebugValue } from 'jotai/devtools'
const DebugAtoms = () => {
useAtomsDebugValue()
return null
}
const Root = () => (
<Provider>
<DebugAtoms />
<App />
</Provider>
}

What's Changed

• fix(utils): fix memory leaks and other issues in atomWithObservable by @​TobiasWalle in pmndrs/jotai#1170
• refactor(urql): atomWithQuery with fixing tests by @​dai-shi in pmndrs/jotai#1179
• feat(devtools): expose useAtomsDebugValue from jotai/devtools by @​dai-shi in pmndrs/jotai#1184

Full Changelog: https://github.com/pmndrs/jotai/compare/v1.6.7...v1.7.0

v1.6.7

React 18 behaves slightly differently from React 17 and some people reported extra re-renders. While extra re-renders without commits are expected, we improved it with early bail out. Now, primitive atoms won't re-render with the same value. Derived atoms can still re-render without commits, but it's intentional.

What's Changed

• fix(utils): atomWithObservable: fix ReferenceError with BehaviourSubject (#1156) by @​TobiasWalle in pmndrs/jotai#1157
• fix(core): do not re-render if value is the same by @​dai-shi in pmndrs/jotai#1159

... (truncated)

Commits

• 3f4176e 1.7.0
• c3a1364 chore(deps): update dev dependencies (#1187)
• 715055a feat(devtools): expose useAtomsDebugValue from jotai/devtools (#1184)
• 6a15db3 fix lint
• e61cb85 refactor(urql): atomWithQuery with fixing tests (#1179)
• d087145 fix(utils): fix memory leaks and other issues in atomWithObservable (#1170)
• 5b99f44 refactor(tests): better handling with React 18 behavioral difference (#1185)
• 1100d96 1.6.7
• 8924b0f chore(deps): update dev dependencies (#1173)
• 08c3b53 fix(core): do not re-render if value is the same (#1159)
• 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 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)