Closed navihtot closed 4 months ago
@navihtot Sorry to hear you're having trouble. It's hard to tell the source from what you've provided, but from the ../
s in the error stack, it could be how you've defined the location of your handler. The AWS Lambda container makes use of NODE_PATH
to find layer-installed dependencies, and we've seen that defining the handler path starting from ./
can complicate how the path is interpreted.
I'm not familiar with esbuild
, but you may want to inspect the zip file Serverless produces: if esbuild
transpiles to cjs, you might not have a deployed mjs handler file.
You shouldn't have to exclude newrelic
, unless you've defined it as a dependency in your local project. I'd recommend defining it as one of your devDependencies, so it's not bundled in your deployment package.
I'd recommend opening a ticket with Support, who can help you work through common setup issues: https://support.newrelic.com/s/
Thank you for your reply. I've tried with different approaches. With and without manual wrapping. I managed to get my code to execute without errors. However the "invocations" still don't end in new relic. I've submitted the ticket for the support as well with more detail. In the end, after all tries, it looks to me like maybe the new relic extension works but doesn't find anything to send for some reason
Closing this issue as you created support request for this.
closing this issue
Hi, I'm using:
serverless-esbuild
I get next error:
I've tried with
manualWrapping: true
and wrapping it in the code, but then I get:I'm not sure what am I doing wrong. Serverless.yml part:
and manual wrapping I've tried: