Paul Myburgh

Hahah awesome! Glad to hear its all working, and cheers for the kind words! :) Appreciate your share on Twitter the other day too - it really pumped up the...

Oh jeeze, can't believe I forgot about the article! Yea, loved it- really nice and concise introduction in a great format. Also nice that you went into some of the...

Hi @xeoneux , and thanks glad you're enjoying the library :) Also, thanks for trying to get an example put together with Next.js! Are you still having the issues? I...

Hi @julianeden , This is a good idea - I'll look into adding a Typedoc which is generated directly from the types and with additional information and examples where relevant....

Hi @wnz99 , Yep just wanting to get all the method descriptions in and hide internal options which shouldn't be documented and clog up the Typedoc. Actually a really cool...

@julianeden @wnz99 I've created the start of the Typedoc reference for Pullstate. There's still a lot to cover, but at least its all laid-out now. The part that's pretty much...

Ah I thought it was linked there already! Maybe I somehow removed it during the last doc update... Will update it again, thanks for pointing it out. Glad to hear...

That's an interesting use case. The thing about Pullstate is that it gives you a lot of rope to do what you want with it. It should be flexible enough...

Unfortunately, currently reactions only support synchronous updates. The current way to do asynchronous updates would be to use a subscription instead, something like this: ```js async function doAsyncStuff(theme) { //...

> `Error: [Immer] An immer producer returned a new value *and* modified its draft. Either return a new value *or* modify the draft.` That is a weird message, as it...