You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it could be useful with async methods too, when you not only want to prevent abuse, but also don't want the regex matching to block other work, which can be important in a server context.
We could do the matching on a worker thread and then send the result back to the main process. This should be possible on both Node.js and the browser.
This is not something I plan to work on, but a good pull request would be welcomed if you need this.
I think it could be useful with async methods too, when you not only want to prevent abuse, but also don't want the regex matching to block other work, which can be important in a server context.
We could do the matching on a worker thread and then send the result back to the main process. This should be possible on both Node.js and the browser.
This is not something I plan to work on, but a good pull request would be welcomed if you need this.
See https://github.com/sindresorhus/crypto-hash/blob/main/index.js for an example of how it could be done.
The text was updated successfully, but these errors were encountered: