Sentry Console Logging Integration not working in AWS Lambda

[InterstellarStella]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nuxt

SDK Version

10.25.0

Framework Version

"nuxt": "^4.2.1"

Link to Sentry event

No response

Reproduction Example/SDK Setup

Full reproduction setup provided in the shadow Linear ticket.

Steps to Reproduce

this might also be a Nuxt issue -- has anyone actually had the console logging integration working in their Nuxt deployment?

For our deployment to AWS Lambda, we are running nuxt build with aws-lambda as the nitro preset (in nuxt.config.ts), and then taking the server portion of the output (the part that is relevant for this issue) and dropping it into the lambda function. As per the instructions for Sentry, I add an environment variable to the lambda that loads the sentry server config first:

NODE_OPTIONS

--import ./.output/server/sentry.server.config.mjs

And otherwise, the lambda runs in Node 22 with .output/server/index.handler set as the handler.

Expected Result

Console logs are reported in Sentry.

Actual Result

Console logs are not reported in Sentry.

Locally (using nuxt dev), I've had success adding a consola reporter. However, that appears not to translate over into working in AWS Lambda, as I deployed that up and no logs came in over the evening and last night. Based on that, I'm thinking this might also be a Nuxt issue.

Additional Context

No response

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1177

[s1gr1d]

Hi, what exactly is deployed here?

I just tried the example and deployed the zipped server folder content. This means, that the Sentry config file is located on the root-level. If I set the env value to --import ./sentry.server.config.mjs, I am able to see the logs.