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
Running a deno install in a docker successful caches deps on subsequent builds but with some caveats.
Some packages are still being downloaded every time at runtime
Ah, the issue is that we only cache the root export from @hono/hono. This was sort of intentional, but now I'm thinking that behavior may be confusing. I'll open a PR
…#26501)
Fixes#26498.
This was a sort of intentional decision originally, as I wanted to avoid
caching extra files that may not be needed. It seems like that behavior
is unintuitive, so I propose we cache all of the exports of listed jsr
packages when you run a bare `deno install`.
…#26501)
Fixes#26498.
This was a sort of intentional decision originally, as I wanted to avoid
caching extra files that may not be needed. It seems like that behavior
is unintuitive, so I propose we cache all of the exports of listed jsr
packages when you run a bare `deno install`.
Version: Deno 2.0.0
Running a
deno install
in a docker successful caches deps on subsequent builds but with some caveats.Some packages are still being downloaded every time at runtime
Repro: https://github.com/kadumedim/deno-hono
Tested locally and on Railway.
Logs from Railway (ignore stderr)
Build:
Deploy:
The text was updated successfully, but these errors were encountered: