grim imp
I tried using it on a dockerfile, if I cache my main entrypoint (main.ts) it downloads at build time on every build, if I cache deno.json it downloads at runtime... Where is this "cache" happening? Am I missing something out?
I'm using --lock=deno.lock and deploying through a Dockerfile on Railway.app (afaik they fully utilize docker cache layer)
leaden gull
Do you have any dependencies defined in Deno.json?
If you only use inline specifiers in your main file then keep using deno cache or replace it with deno install --entrypoint
grim imp
If you only use inline specifiers in your main file then keep using `deno cache`...
yes, hono.
you can check the repo here https://github.com/kadumedim/deno-hono/blob/main/deno.json
leaden gull
deno install in repo root should take cache of caching everything necessry
grim imp
will give it a try, thanks
grim imp
@leaden gull now it is indeed caching, thanks.
There's just this one package that keeps getting downloaded at runtime, what could it be?
leaden gull
Yikes, hard to say on top off my head.
Could you please open an issue about it?
I think it might be related to types but I'm not sure
novel talon
maybe related with https://github.com/denoland/deno/issues/26180? i do have the same issue since i have to run it without the --cached-only flag and it downloads stuff as well
grim imp
Opened an issue
https://github.com/denoland/deno/issues/26498