Optical Disc 💿
deno_runtime NpmResolver like the CLI?
As far as I can tell, if I want to embed Deno in my Rust application using deno_core and deno_runtime, I would effectively need to implement my own npm: specifier resolution.
https://docs.rs/deno_node/0.76.0/deno_node/trait.NpmResolver.html
I found this trait I can implement, but what I really want is for module imports to just be identical to how they are when running code from the plain Deno CLI.
People seem to say frequently that deno_runtime is the solution for copying the Deno CLI's behavior in a custom executable, but I can't find any existing structures that mimic the module-graph mapping behavior that is included with the CLI, so wouldn't I be better off just forking the CLI code?
7 replies
Unable to build crate with deno_runtime 0.139.0 or 0.140.0, due to version numbering in deno_ast
The two most recently released versions of the deno_runtime crate cannot build at all, due to its build dependency deno_ast ^1.0.1.
The latest version of deno_ast is 0.32.1, but cargo reads that as a lower version number, and therefore refuses to use it.
The exact version 1.0.1 of deno_ast was yanked from crates.io, so it can't be used for building.
4 replies