using kill() does not fully reset state

[reviewher]

https://github.com/alewin/useWorker/blob/master/packages/useWorker/src/useWorker.ts#L64

If the kill method is called from user code, isRunning is never reset and https://github.com/alewin/useWorker/blob/master/packages/useWorker/src/useWorker.ts#L149 error is tripped the next time the worker is used.

setWorkerStatus(WORKER_STATUS.ERROR) or isRunning.current = false in that spot fixes the problem

[ashish-r]

In this sorting example also, the kill functionality is not working.

The issue for kill functionality is in version 3 and version 4. It was working fine in version 2

@alewin @zant

[ashish-r]

Created the PR for fix here

@alewin @zant please review

[Arif-un]

Still the same problem, any update on this issue?

[ghost]

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。

[ashish-r]

@Arif-un this pr is still not merged.

@alewin @zant guys the PR is approved, anything I should change/take care of? If not can we please merge?

[sheron184]

Is this issue fixed?

[alewin]

released [email protected] with the fixes ( #122 )
thanks @ashish-r

Apologies for the long wait, but due to personal and work-related reasons, I wasn’t able to maintain the library.
I’m well aware that forks and alternatives have emerged in the meantime, and I’m glad for it because the library was intentionally open-source with an MIT license to prevent issues like this.

Together with the new maintainer, @naorpeled, we are working to stabilize useWorker and add new features in the coming months. :)