zustand 3 milestones

Let’s collect some,

• Concurrent React, are we ready for it?
• Simpler API?

currently

const [useStore, api] = create(set => ({ set, count: 0 }))

const count = useStore(state => state.count)

const count = api.getState().count
const unsub = api.subscribe(count => console.log(count), state => state.count)
api.setState({ count: 1 })

why not

const useStore = create(set => ({ set, count: 0 }))

const count = useStore(state => state.count)

const count = useStore.getState().count
const unsub = useStore.subscribe(count => console.log(count), state => state.count)
useStore.setState({ count: 1 })

vanilla users wouldn’t name it “useStore”

const api = create(set => ({ set, count: 0 }))
const count = api.getState().count

it would mean we’re now api compatible with redux without doing much.

with a little bit of hacking it could also be made backwards compatible by giving it a iterable property. i’ve done this before with three-fibers useModel which returned an array once, but then i decided a single value is leaner.

@JeremyRH

[JeremyRH]

Looks like a new React hook might solve this: https://github.com/reactjs/rfcs/pull/147

[timkindberg]

Another idea for clean api would be to return the api object and have the hook be a property on it.

const store = create(set => ({ set, count: 0 }))

const count = store.use(state => state.count)

const count = store.getState().count
const unsub = store.subscribe(count => console.log(count), state => state.count)
store.setState({ count: 1 })