v2.4.1

Bug fixes

• Set defaults.batchUpdates to false as it's a potential breaking change. Making it opt-in for now

v2.4.0

New features

Updates are now batched by default even across actions and stores. It means that calling setState will no longer trigger a synchronous re-render but it will schedule an update that will triggered on next tick.
This behaviour can be disable by setting defaults.batchedUpdates = false

v2.3.3

Optimisations

• Discard store update if next state is shallow equal to current state

v2.3.2

Bug fixes

• Fix Flow type definition for default store type

v2.3.1

Bug fixes

• Fix selectors triggering unnecessary re-renders

v2.3.0

New features

• Allow defaults.devtools to be a function to customise Redux Devtools store options

v2.2.0

New features

• added batch API to easily batch multiple setState calls and actions. It is basically a re-export of React.unstable_batchedUpdates API.

Bug fixes

• sweet-state now fully works under React StrictMode, even while in dev mode. Now sweet-state is more compliant with the future React Concurrent

v2.1.1

New features

• onCleanup API for containers, triggered after a container gets removed from the tree

Bug fixes

• Fix stores not being cleared if no listeners and container removed from the tree
• Fix createStore store types, forcing initialState to be an object as other types where never really supported

v2.0.2

• Fix security concern by not using eval in devtools

v2.0.1

• Fix issue when React batching was skipping components updates