Accept a module path instead of code string?

It seems this library current accepts code string (and somehow tries to convert it to CommonJS 🤔) but can it accept a module path? I guess it should be possible to generate a code to import the module from the given path.

Start by reading the library's public API and the current code-string conversion path to understand how worker modules are loaded. Determine how a module path should be accepted and how generated import code should behave, then verify the new path-based usage alongside the existing code-string behavior.

Escrito por el modelo de indexación a partir del texto del issue.