Closed cristinecula closed 4 years ago
The haunted state is updated twice in the same update-render-loop, causing the scheduler to miss running the effects upon component initialization.
To fix it, I move the promise resolution inside the haunted loop, by the use of use-promise.
:tada: This PR is included in version 6.0.4 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
The haunted state is updated twice in the same update-render-loop, causing the scheduler to miss running the effects upon component initialization.
To fix it, I move the promise resolution inside the haunted loop, by the use of use-promise.