Repository navigation
Comparing changes
Open a pull request
base repository: pmndrs/zustand
base: v5.0.15
head repository: pmndrs/zustand
compare: v5.0.16
- 11 commits
- 12 files changed
- 12 contributors
Commits on Aug 17, 2026
-
Configuration menu - View commit details
-
Copy full SHA for b126c33 - Browse repository at this point
Copy the full SHA b126c33View commit details
Commits on Aug 19, 2026
-
docs: fix broken migrating-to-v5 link in README (#3567)
The `createWithEqualityFn` note linked to ./docs/migrations/migrating-to-v5.md, but the migration guides live under ./docs/reference/migrations/. Point the link at the existing file so the anchor resolves. Claude-Session: https://claude.ai/code/session_012TECwEsvMbRbisqtW2R2iV Co-authored-by: fandi <[email protected]> Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ea612a5 - Browse repository at this point
Copy the full SHA ea612a5View commit details -
Configuration menu - View commit details
-
Copy full SHA for f094eeb - Browse repository at this point
Copy the full SHA f094eebView commit details
Commits on Aug 24, 2026
-
docs(create): document that state cannot be read during initialization (
#3569) * docs(create): document that state cannot be read during initialization The store api passed to the state creator function is not usable for reading state while that function runs: get() and store.getState() return undefined, and store.getInitialState() throws "Cannot access 'initialState' before initialization". Per the discussion, this is a designed limitation rather than a bug, so document it in the create and createStore troubleshooting sections. Ref: #3529 * docs(create): shorten init-time state access note to a one-line caveat Per review feedback, the troubleshooting section was too long for such a subtle behavior. Replace it with a one-line note on the stateCreatorFn parameter in both create and createStore. --------- Co-authored-by: fandi <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b57db4f - Browse repository at this point
Copy the full SHA b57db4fView commit details
Commits on Sep 29, 2026
-
Clarify maintainer-guided contribution workflow (#3587)
Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: dai-shi <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d7a5583 - Browse repository at this point
Copy the full SHA d7a5583View commit details
Commits on Oct 22, 2026
-
perf(react): don't memoize getServerSnapshot in useStore (#3563)
React only calls getServerSnapshot during hydration/server rendering and never retains or compares its identity (checked across 18.0-19.2, Fizz, the shim, preact/compat and RN), so the useCallback around it was pure per-render overhead: one hook slot, a deps array and a closure. Dropping it saves ~13% of useStore's per-render allocation and a few bytes. Co-authored-by: Samuel Attard <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for dac22e1 - Browse repository at this point
Copy the full SHA dac22e1View commit details -
fix(devtools): apply serialize.reviver when parsing devtools messages (…
…#3568) connect() forwards `serialize` to the extension for outgoing state, but incoming ACTION/ROLLBACK/JUMP_TO_STATE/JUMP_TO_ACTION messages were parsed with a bare JSON.parse, so a configured reviver never ran. Types like Immutable.js collections came back as plain objects after using devtools' Jump/Revert/Rollback controls. Fixes #2561 Co-authored-by: koreahghg <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d867e6f - Browse repository at this point
Copy the full SHA d867e6fView commit details -
fix(devtools): preserve shared connections during store cleanup (#3580)
* fix(devtools): preserve shared connections during store cleanup * test(devtools): cover cleanup review edge cases Cover independent and shared connections using the same name, and verify that repeated cleanup preserves replacement registrations. Use a curly block for the cleanup guard. * fix(devtools): check store identity during cleanup Pass the store API to tracked connection cleanup so an older store cannot remove a replacement registration. Remove the cleanup flag and cover replacement before the first cleanup call. --------- Co-authored-by: chungyo <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a1fea2e - Browse repository at this point
Copy the full SHA a1fea2eView commit details -
fix(persist): preserve external devtools action arguments (#3592)
Co-authored-by: Godsdar <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for da2706c - Browse repository at this point
Copy the full SHA da2706cView commit details -
chore(deps): update dev dependencies (#3593)
* chore(deps): update dev dependencies * downgrade @types/node
Configuration menu - View commit details
-
Copy full SHA for b488323 - Browse repository at this point
Copy the full SHA b488323View commit details -
Configuration menu - View commit details
-
Copy full SHA for 382d29c - Browse repository at this point
Copy the full SHA 382d29cView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.0.15...v5.0.16