DENO_DIR cache *maybe* no longer works

[hayd]

Previously

import type {
  Context,
  APIGatewayProxyEvent
} from "https://deno.land/x/lambda/mod.ts";

etc.

the deps and gen were correctly cached (from the layer and the function code), this seems to no longer be the case.

It's unclear to me if it's a zipping issue or due the filenames being renamed (now there's hashes in the name).

---

I'm not 100% sure this is an issue, but have a suspicion... needs investigate (and ideally a test).

[hayd]

Specifically deno.land/x/lambda should not be fetched during tests?

[hayd]

So, previously the https://deno.land/x/lambda/mod.ts and types.d.ts were prepopulated from the current dir (avoiding the fetch). This is no longer the case :/

I am not sure the best solution here... perhaps simply not using https://deno.land/x/lambda/mod.ts ? 😢

[hayd]

Use deno-lambda with docker is my recommendation for this.

Deno uses more opaque/clever caching for local file compiled assets than it once did. I haven't looked into this in a while / am not sure how much/if any is exposed so mv assets could work.