Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
|
Size Change: -86.9 kB (-82.77%) 🏆 Total Size: 18.1 kB 📦 View Changed
|
This was referenced Jun 11, 2026
Merged
Merged
* [v3] drop old node * fix test * fix again
Merged
Merged
* [v3] drop rollup * strict module * some fixes
Merged
* [v3] drop old React * fix ci test
Merged
This was referenced Jul 16, 2026
Merged
* [v3] redesign buildingBlocks * use key constants for better readability
Member
Author
|
/ecosystem-ci run |
Ecosystem CI Output |
| rerender() | ||
| value = store.get(atom) | ||
| } | ||
| useEffect(() => store.sub(atom, rerender), [store, atom]) |
There was a problem hiding this comment.
There is a slight behavioral difference in useAtomValue between v2 and v3. I'm not sure if this is intentional or could cause an issue.
// before (in useAtomValue)
useEffect(() => {
const unsub = store.sub(atom, () => {
// ...
rerender()
})
rerender() // <-- rerender was called on mount
return unsub
}, [store, atom, delay, promiseStatus])
// after (in useAtomValueRaw)
useEffect(() => store.sub(atom, rerender), [store, atom])In v2, rerender() was explicitly called on mount, whereas in v3 it seems to only be triggered by the subscription.
Collaborator
There was a problem hiding this comment.
This is intentional and documented.
Member
Author
There was a problem hiding this comment.
Yes, this is intentional and one of the biggest reasons for the major bump. Suggestions are welcome to improve the docs.
There was a problem hiding this comment.
I can't open a PR myself (locked to collaborators), so here's an attempt to better explain the differences between the three hooks: https://github.com/pmndrs/jotai/compare/v3...Wendystraite:jotai:v3_docs?expand=1
3 tasks
Member
Author
|
@arjunvegda Could you work on migrating jotai-devtools? |
Merged
Member
Author
|
/ecosystem-ci run |
Ecosystem CI Output |
Member
Author
|
/ecosystem-ci run |
Ecosystem CI Output |
Collaborator
|
/ecosystem-ci run |
Ecosystem CI Output |
* doc: explain loadable deprecation in v3 doc * doc: explain differences between atom hooks * doc: reword useAtomValueRaw return value explanations Co-authored-by: Daishi Kato <dai-shi@users.noreply.github.com> --------- Co-authored-by: Wendy FOUCHTER <wendy.fouchter@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.