`deno run` that never writes to `DENO_DIR` or `deno.lock`?
I am working on an application that embeds a
The plugins are folders that are included in our app bundle, which contain deno configuration and
Because we need to sign our app bundle, and some plugins are bundled within the app bundle, we run into the issue where the signature will be invalidated due to
We don't want to use
It seems like some combination of
denodeno runThe plugins are folders that are included in our app bundle, which contain deno configuration and
.tsBecause we need to sign our app bundle, and some plugins are bundled within the app bundle, we run into the issue where the signature will be invalidated due to
deno run --cached-onlydeno.lockdeno-depsWe don't want to use
--frozencompileIt seems like some combination of
--cached-only--no-remote--vendor
