As seen in ec2b7cedcb617c90d54a73eb8a518e886b31a58e:
Because the module code is run within an iframe where Wombat is active, attempts to create a new Worker() using module code will fail because Wombat will rewrite the file location, thinking it's referencing a collection-specific archive resource as opposed to a static file.
One workaround I've found for this is to convert the worker function into a Blob, and generate a URL for it--that way, Wombat won't rewrite the URL in the same way. The implementation can be seen in #8.
As seen in ec2b7cedcb617c90d54a73eb8a518e886b31a58e:
Because the module code is run within an
iframe
where Wombat is active, attempts to create a newWorker()
using module code will fail because Wombat will rewrite the file location, thinking it's referencing a collection-specific archive resource as opposed to a static file.