tmcw
Is there any way to get Deno to not statically analyze import()?
Another issue for another part of this - doesn't seem like
"" +
works for npm: packages - https://github.com/denoland/deno/issues/204798 replies
Is there any way to get Deno to not statically analyze import()?
that's been a fairly tough one to work with - with val.town at least there are certain dependencies that just break the evaluation server until it restarts, though evaluations are happening in a Worker
8 replies
Is there any way to get Deno to not statically analyze import()?
there's a bug report i've commented on at https://github.com/denoland/deno/issues/18557 - if you have a dynamic import that points to a module that has a
git+
dependency, your import()
method is permanently broken8 replies
Can I pre-cache dependencies that I specify using npm:?
Ah, using vendor triggers some different permissions. That's why I wasn't using it. Sorry, this codebase is a little zany - we're using WebWorker's ability to run with reduced permissions, so there's a catch-22 where if I vendor dependencies, then Deno tries to use vendored deps within the WebWorker, which doesn't have
--allow-read
. Maybe there's a way to exclude stuff from being vendored21 replies
Using dynamic import with npm compatibility gives intermittent error "__DENO_NODE_GLOBAL_THIS_167935
filed a bug with the repro: https://github.com/denoland/deno/issues/18343
12 replies
Using dynamic import with npm compatibility gives intermittent error "__DENO_NODE_GLOBAL_THIS_167935
okay i think i found a workaround - if you import something from npm on the top level before you import something from npm in an import, then it works
12 replies
Using dynamic import with npm compatibility gives intermittent error "__DENO_NODE_GLOBAL_THIS_167935
tracked the internals down to https://github.com/denoland/deno/blob/7d9653d51fb0c4d3844f61e1214b6bddc50d2cef/ext/node/lib.rs#L401 - not like that's the cause
12 replies