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
I'm building something on top of deno_runtime and I'm using MainWorker::evaluate_module. The problem I have is that if I evaluate a module that has already been evaluated, JsRuntime::mod_evaluate panics.
I can of course keep track of what I send to MainWorker::evaluate_module and avoid evaluating the same module twice. But I don't have control over what's imported inside modules. For example, if I evaluate module A which imports module B, JsRuntime::mod_evaluate will panic if I later evaluate module B.
With the public API, is it possible to know which modules have already been evaluated? Can I somehow know that module B has been evaluated?
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
-
I'm building something on top of
deno_runtime
and I'm usingMainWorker::evaluate_module
. The problem I have is that if I evaluate a module that has already been evaluated,JsRuntime::mod_evaluate
panics.I can of course keep track of what I send to
MainWorker::evaluate_module
and avoid evaluating the same module twice. But I don't have control over what's imported inside modules. For example, if I evaluate moduleA
which imports moduleB
,JsRuntime::mod_evaluate
will panic if I later evaluate moduleB
.With the public API, is it possible to know which modules have already been evaluated? Can I somehow know that module
B
has been evaluated?Beta Was this translation helpful? Give feedback.
All reactions