Erica Windisch
Erica Windisch
I tested and it is also working in Safari, but is not working in Chrome. I have tried this on two different MacOS BigSur systems.
ping @austinhuminski
WIP tree: https://github.com/ewindisch/iopipe/tree/i_promise_you
/cc @dustingetz (requested this via gitter.im)
Correct. The import seems to look in the "LAMBDA_TASK_ROOT" for the handler. ``` $ serverless invoke -f hello -l { "errorType": "Error", "errorMessage": "Cannot find module '/var/task//opt/nodejs/node_modules/@iopipe/iopipe'", "stackTrace": [ "...
same error if I use `@iopipe/iopipe.handler` ``` { "errorType": "Error", "errorMessage": "Cannot find module '/var/task/@iopipe/iopipe'", "stackTrace": [ " at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)", " at Function.Module._load (internal/modules/cjs/loader.js:562:25)", " at Module.require (internal/modules/cjs/loader.js:690:17)", "...
@mhart I have a layer that contains my handler. In my personal use-case, that handler is a wrapper that then does an import and load of another handler... but it's...
@mhart The official AWS ones do not for NodeJS, but this is confirmed to work with the official Java and Python runtimes from AWS . I've been nudging AWS to...
My testing has been unsuccessful in using path traversals via '..' to enable this /w the official runtime. Lambda has always supported importing from node_modules, this would ideally just allow...