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
Is your feature request related to a problem? Please describe.
We currently have one Node.js wrapper newrelic-lambda-wrapper.handler. To use it for ESM based lambdas, you have to set the env var of NEW_RELIC_USE_ESM. You also have to set NODE_OPTIONS='--experimental-loader newrelic/esm-loader.mjs. The problem with having 1 wrapper is it has to be entirely synchronous. This was fine up until our investigations of supporting lambda response streaming(newrelic/node-newrelic#2901). The lambda runtime detects response streaming from a symbol on the handler. Our agent is propagating this handler to the wrapped function but the layer wraps the wrapped function and the symbols are removed.
Feature Description
Publish 2 different lambda wrappers. Update README and docs phasing our NEW_RELIC_USE_ESM in favor of the new esm wrapper.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We currently have one Node.js wrapper
newrelic-lambda-wrapper.handler
. To use it for ESM based lambdas, you have to set the env var ofNEW_RELIC_USE_ESM
. You also have to setNODE_OPTIONS='--experimental-loader newrelic/esm-loader.mjs
. The problem with having 1 wrapper is it has to be entirely synchronous. This was fine up until our investigations of supporting lambda response streaming(newrelic/node-newrelic#2901). The lambda runtime detects response streaming from a symbol on the handler. Our agent is propagating this handler to the wrapped function but the layer wraps the wrapped function and the symbols are removed.Feature Description
Publish 2 different lambda wrappers. Update README and docs phasing our
NEW_RELIC_USE_ESM
in favor of the new esm wrapper.The text was updated successfully, but these errors were encountered: