Dynamic file imports inside JSR packages not working

[davideperozzi]

I'm currently trying to migrate to JSR with deno 2.0. My package has dynamic imports like:

await import('file://' + file);

And after I published my package to JSR and tried to run it locally after installing it globally, I got this error:

TypeError: Module not found "https://jsr.io/{..pathToFile}"

It somehow tries to import it from JSR, despite having it marked as a local import. I don't know if this is a bug or expected behavior? I assume you can't dynamically import from a package installed from JSR? Seems limited to me. Might have to move away from deno as I don't want to reverse all my changes.

Anyone has a smiliar issue and figured it out? Would appreciate the help!

[grenierdev]

I'm having the same issue with https://jsr.io/@baseless/client/0.3.0-rc.11/cli.ts.

deno run -A client/cli.ts ../app/src/app.ts -d works.
deno run -A jsr:@baseless/client@0.3.0-rc.11/bls ../src/src/app.ts -d don't.

I tried @std/path/resolve, import.meta.resolve, forcing file:// as you did.

I understand the security aspect of not allowing importing modules at runtime, but it's exactly what I'm trying to do. Like Tanstack Router, I want to run a command to load a module and extract stuff from the module.

This use-case is legit.

[davideperozzi]

@grenierdev Yeah, security is a big issue with this. A dependency could just import random files without the user even knowing it. Maybe this could be solved through an extra flag? Or make the user somehow aware of what files will be imported by which module. Since this works with "deno.land modules", I expected it to work with JSR as well.