Andy Hayden

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......

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...

Atm `CMD ["foo/bar/baz.handler"]` is the way forward. In some sense that's not a workaround but has always been the way to reference files not at the top level. It's unclear...

Not looked into this but my suspicion is what should be done is cd into /var/task and realpath the WORKDIR (initial directory). ``` # realpath -m --relative-to="/var/task/" "/var/task/foo/bar/baz.handler" foo/bar/baz.handler ```...

Does the SAM example deployment no longer work? (It should really be added to the test suite. I'd missed that it wasn't tested.) I don't understand the need for this...

Can you move these back up a directory? (I think it should work without the /deno/ change.) If not, I can fix it later. Thanks again for the investigation. 👍...

I've got it: ```makefile build-HelloWorldFunction: DENO_DIR=.deno_dir deno cache hello.ts cp -R .deno_dir/gen/file$(CURDIR)/ .deno_dir/LAMBDA_TASK_ROOT ```

sam respects .npmignore, so those wouldn't be included in the deployment.

At least my Makefile required tabs 😞

and still `sam local invoke` doesn't work: ``` {"errorType":"exitError", "errorMessage":"RequestId: 981552a1-0545-12ff-bcf5-8ecb4bf88539 Error: Couldn't find valid bootstrap(s): [/var/task/bootstrap /opt/bootstrap]"} ``` strange. Are we going down the wrong path here? Very confusing....