Skip to content

No matching export in "node_modules/@sentry/node/build/esm/index.js" for import "wrapMcpServerWithSentry" #16275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 tasks done
pedroSoaresll opened this issue May 13, 2025 · 3 comments

Comments

@pedroSoaresll
Copy link

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/aws-serverless

SDK Version

9.17.0

Framework Version

NodeJS v22.12.0, Serverless Framework 4.14.3

Link to Sentry event

No response

Reproduction Example/SDK Setup

Image

Image

Steps to Reproduce

Image

Expected Result

My tests and serverless build/deploy to pass

Actual Result

Error: R] No matching export in "node_modules/@sentry/node/build/esm/index.js" for import "wrapMcpServerWithSentry"

    node_modules/@sentry/aws-serverless/build/npm/esm/index.js:1:2227:
      1 │ ...hMonitor, withScope, wrapMcpServerWithSentry, zodErrorsIntegrati...
        ╵                         ~~~~~~~~~~~~~~~~~~~~~~~
@andreiborza
Copy link
Member

Hi @pedroSoaresll, thanks for writing in.

Are you sure you're on 9.17.0? I've tried to reproduce this, but both the lambda layer and just installing @sentry/aws-serverless manually and running Sentry.wrapMcpServerWithSentry.toString() seems to work for me.

Do you have a reproduction repo?

@pedroSoaresll
Copy link
Author

Hey @andreiborza, thanks for taking the time for this, I will try to create a reproduction repo and share here later. I will return here soon.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 May 13, 2025
@getsantry getsantry bot moved this from Waiting for: Product Owner to Waiting for: Community in GitHub Issues with 👀 3 May 13, 2025
@pedroSoaresll
Copy link
Author

@andreiborza I discovered that the problem was cache on CI environment. Before building an example for you, to demonstrate the problem, I resolve to clean dependencies installation cache on CI and everything works as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants