This fixes module resolution issue for React Native users.

What's Changed

refactor(traditional): remove duplicated ExtractState type declaration by @shinhyogeun in #2982
fix(package): react-native condition by @dai-shi in #3087

New Contributors

@zbeyens made their first contribution in #2958
@samirhembrom made their first contribution in #2963
@alimertcakar made their first contribution in #2980
@sidahmedabdelillah made their first contribution in #2978
@Sunjae95 made their first contribution in #2994
@chervyakovru made their first contribution in #3001
@andriyor made their first contribution in #3002
@theperfectpunk made their first contribution in #2998
@locothedev made their first contribution in #3004
@paulschoen made their first contribution in #3008
@mooalot made their first contribution in #3011
@rn0614 made their first contribution in #3037
@dngur9801 made their first contribution in #3042
@Shashikantyadavv made their first contribution in #3045
@mtilda made their first contribution in #3053
@jroitgrund made their first contribution in #2995
@oduntane made their first contribution in #3080
@B1u3B01t made their first contribution in #3082
@vikpe made their first contribution in #3094
@wy-luke made their first contribution in #3100
@shinhyogeun made their first contribution in #2982

Full Changelog: v5.0.3...v5.0.4

🎉🎉🎉 Zustand v5 🐻🐻🐻

TL;DR

No new features
Drop many old things
Migration from v4 should be smooth.

Changes in v5

Drop default exports
Drop deprecated features
Make React 18 the minimum required version
Make use-sync-external-store a peer dependency (required for createWithEqualityFn and useStoreWithEqualityFn in zustand/traditional)
Make TypeScript 4.5 the minimum required version
Drop UMD/SystemJS support
Organize entry points in the package.json
Drop ES5 support
Stricter types when setState's replace flag is set
Persist middleware behavioral change
Other small improvements (technically breaking changes)

Migration Guide

Read the migration guide carefully:
https://github.com/pmndrs/zustand/blob/main/docs/migrations/migrating-to-v5.md

Frequently Reported Issue

During the RC period, some users encountered the following infinite loop error:

Uncaught Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

This case was already a non-ideal behavior in v4 but appears more explicitly as an error in v5. While there are several ways to resolve this, using useShallow often fixes the problem.