'How does Deno resolve Rust plugins when deployed

I'm having trouble understanding the deployment model for creating Deno + Rust plugins. My application has a need for certain performance elements which are in Rust and a plugin is perfect. I've read articles such as https://alexandrempsantos.com/deno/creating-a-deno-plugin/ which explains developing the plugin.

What is completely unclear to me is if Deno uses ESM to resolve dependencies, what happens when you add a Rust dependency? I can see where it happens ie Deno.openPlugin('./rust-plugin/lib.rs'); seems to do.

Adding in the flags on the CLI -unstable --allow-plugin is also necessary.

The confusing part is how it resolves that dependency when deployed or run. Does Deno consume the raw .rs file and compile on the fly at runtime?

rust deno

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source

'How does Deno resolve Rust plugins when deployed

Sources

Related Questions