Skip to content

UMD builds are bugged: workers are loaded in "module" mode, but webpack worker builds dont work with that #881

@machineonamission

Description

@machineonamission

Describe the bug
this line here

new Worker(new URL(classWorkerURL, import.meta.url), {
type: "module",
}) :

always loads the workers in module mode. BUT webpack umd modules are NOT in module mode. so importScripts silently fails and ffmpeg never loads.

webpack outputs some bizarre "import" code

Image and this is what webpack outputs for the module import code, a bare function that always fails. Image

To Reproduce
make a copy of the UMD builds from node, and try to load them from a non-module source

Expected behavior
the modules, in umd mode, should be loaded in classic mode, not umd

Screenshots
see above

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: MS Edge
  • Version: 0.12.10

Additional context
this bug was a NIGHTMARE to track down. the errors are caught and silently fail with no traceback. horrible.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions