You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose module resolution code in a public library (like deno_runtime)
#36952
The desire for this has been brought up before (#21968, https://questions.deno.com/m/1204794589064462346, #9595)
It would be nice if module loader (and worker lifecycle) could be extracted into separate published crates like runtime and core are.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I attempted to embed Deno in a Rust app to serve a server-rendered web page from JS framework (SvelteKit) as part of a Rust web server.
deno_runtime::worker::MainWorkerneed a module loader, which the CLI provides (https://github.com/denoland/deno/blob/main/cli/module_loader.rs), however it is not exported.The desire for this has been brought up before (#21968, https://questions.deno.com/m/1204794589064462346, #9595)
It would be nice if module loader (and worker lifecycle) could be extracted into separate published crates like runtime and core are.
All reactions