Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Web workers support
See original GitHub issueType of Issue
[ ] Bug Report
[X] Feature Request
Description
I need to use web worker for image processing library, and I am wondering if it is possible to generate a web worker inside the library and make it work out of the box for consumers?
Currently, my workaround is to add an inline script as a blob url and create a worker with it.
However the downside of this workaround is that you won’t be able to use {type: 'module}. and it is not possible to use 3rd party libraries such as rxjs.
A feature: please describe your use case and motivation
It would be very useful if we can generate web workers and integrate them in the library without requiring users to manually configure them.
Expected Behaviour
A feature: do you have a first draft or an idea how to implement?
Not sure if it is possible.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Running code in web workers should be handled at an application level.
iMHO, a library should offer a set of features and than its up to the consumer if these features should be run in a web worker or the not.
Don’t think its possible.
new Worker()requires a URL and that can only be done by the app.