[useSentry] @sentry/ >= 6.18.x causes runtime error

[AzSiAz]

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a minimal reproduction available on Stackblitz.
  • Please install the latest @envelop/* packages that you are using.
  • Please makee sure the reproduction is as small as possible.
• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug
While refactoring my code to use Pothos, I noticed using @envelop/sentry result in

{
  "errors": [
    {
      "message": "Cannot read properties of undefined (reading 'setData')"
    }
  ]
}

To Reproduce
Just use sentry plugin with Pothos framework, exemple repo
https://stackblitz.com/edit/node-qabanz?file=package.json

Expected behavior
No Error

Environment:

• OS: MacOS
• NodeJS: 17 & 16
• @envelop/sentry: 3.1.1
• @envelop/core: 2.1.0

Additional context
I am also using this as server
@graphql-ez/express: 0.9.7,
@graphql-ez/plugin-websockets: 0.10.4,

[MattiaPette]

Hi, I've noticed the same error in my local environment (a simple test project using envelop + sentry), and downgrading @sentry/node and @sentry/tracing to 6.18.1 fixed this for me, the version 6.18.2 doesn't work so the bug may be related to that particular version.

[AzSiAz]

I am also using the latest version of sentry, but I didn't notice any problem with nexus 🤔
I will try later today just in case i missed it

If downgrading sentry is the way to temporary fix this, then perfect I will just wait until upgrading it again until a fix is issued

[AzSiAz]

I tested with 6.18.1 for sentry package and 3.1.1 for @envelop/sentry and it's working as @MattiaPette said

[n1ru4l]

Hey, I updated the issue with the workflow progress for resolving it.

[AzSiAz]

I edited my post with a reproduction

[n1ru4l]

I reduced the reproduction further in https://stackblitz.com/edit/node-kwtsm9?file=src/index.ts

This is not related to pothos at all. I will update the title of this issue.

[AzSiAz]

True, thanks for the update

[pi0neerpat]

In case anyone else encounters this in a RedwoodJS project, hre's what worked for me after nuking node_modules, yarn.lock, and /dist.

    "@envelop/rate-limiter": "^1.0.0",
    "@envelop/sentry": "^3.1.1",
    "@redwoodjs/api": "^0.50.0",
    "@redwoodjs/graphql-server": "^0.50.0",
    "@sentry/node": "6.18.1",
    "@sentry/tracing": "6.18.1",

[HashDot]

I have the same problem with the following packages:

    "@envelop/graphql-jit": "^4.1.0",
    "@envelop/sentry": "^3.1.1",
    "@graphql-yoga/node": "^2.0.0",
    "@sentry/node": "^6.18.1",
    "@sentry/tracing": "^6.18.1",

I tested it with the latest versions and with this downgrade fix. Nothing works.

[n1ru4l]

@HashDot ^6.18.1 will resolve to 6.19.3. You need to pin to the exact version 6.18.1.

See https://semver.npmjs.com/ for more information as well as https://docs.npmjs.com/about-semantic-versioning

In regards to fixing this issue, it seems like there is an unexpected breaking change within sentry. I quickly scanned the sentry issues but could not find one. I will dedicate more time to this issue next week. In the meantime, any help or research (of the sentry changes) is highly appreciated.

[HashDot]

@n1ru4l ty. my bad :)

[n1ru4l]

This is linked to getsentry/sentry-javascript#4731

I created #1367 with a failing test.

Currently, a workaround seems to be adding a import "@sentry/tracing".

[n1ru4l]

@HashDot @AzSiAz @pi0neerpat @MattiaPette can anyone confirm whether this is solved with sentry version 6.19.4 getsentry/sentry-javascript#4731 (comment)?

[MattiaPette]

Hi @n1ru4l !
I've updated to @envelop/core@^2.3.1, @envelop/sentry@^3.4.0, @sentry/node@^6.19.6, @sentry/tracing@^6.19.6 and it's not causing any runtime errors in my project in the limited testing i've done.

Version 6.19.4 works as well with the same results.

Only thing that I'm noticing has changed right now is this log:

Sentry Logger [log]: Integration installed: InboundFilters
Sentry Logger [log]: Integration installed: FunctionToString
Sentry Logger [log]: Integration installed: ContextLines
Sentry Logger [log]: Integration installed: Console
Sentry Logger [log]: Integration installed: OnUncaughtException
Sentry Logger [log]: Integration installed: OnUnhandledRejection
Sentry Logger [log]: Integration installed: LinkedErrors
Sentry Logger [log]: Integration installed: Http
Sentry Logger [error]: Mongo Integration was unable to require `mongodb` package.
Sentry Logger [log]: Integration installed: Mongo

It's probably not related to this issue, will try to investigate further and open another issue if it's needed.

[AzSiAz]

Still need to import import '@sentry/tracing' as soon as I use useSentry from @envelop/sentry (v3.4.0) and I make a query
No bundler on my side just ts-node-dev and tsc to build production version
Tested with @sentry/node & @sentry/tracing version 6.19.4 and 6.19.6 (with fresh node module install)

[n1ru4l]

I am also still experiencing the same issues on 6.19.6 😢 (getsentry/sentry-javascript#4731 (comment))

[jycouet]

Hi @n1ru4l ! I've updated to @envelop/core@^2.3.1, @envelop/sentry@^3.4.0, @sentry/node@^6.19.6, @sentry/tracing@^6.19.6 and it's not causing any runtime errors in my project in the limited testing i've done.

Version 6.19.4 works as well with the same results.

Only thing that I'm noticing has changed right now is this log:

Sentry Logger [log]: Integration installed: InboundFilters
Sentry Logger [log]: Integration installed: FunctionToString
Sentry Logger [log]: Integration installed: ContextLines
Sentry Logger [log]: Integration installed: Console
Sentry Logger [log]: Integration installed: OnUncaughtException
Sentry Logger [log]: Integration installed: OnUnhandledRejection
Sentry Logger [log]: Integration installed: LinkedErrors
Sentry Logger [log]: Integration installed: Http
Sentry Logger [error]: Mongo Integration was unable to require `mongodb` package.
Sentry Logger [log]: Integration installed: Mongo

It's probably not related to this issue, will try to investigate further and open another issue if it's needed.

Did you try adding npm i mongodb?
But yes, I think also it' snot linked to this issue.

[n1ru4l]

So according to getsentry/sentry-javascript#4731 (comment), Sentry, unfortunately, shipped a major breaking change in a minor/patch release.

I updated the documentation to reflect that change in #1407.