[node][8.0.0] TypeError: acs.getCurrentScope is not a function

[lcsvcn]

[node][8.0.0] TypeError: acs.getCurrentScope is not a function

[mydea]

Looking into this some more, in addition to @Lms24 comment above, I think @Mintoo200 your problem is because of https://www.npmjs.com/package/pino-sentry, which uses v7 of the SDK, see https://github.com/aandrewww/pino-sentry/blob/master/package.json#L37. This has to be updated to be compatible with v8!

I opened an issue for this: aandrewww/pino-sentry#68

[lcsvcn]

Started after Dependabot changed from:

7.114.0 to 8.0.0

reverting to 7.114.0 works fine

[mydea]

Hey, thank you for reporting.

Some questions:

1. What node version are you using?
2. Could you share more of your init code, e.g. where in your app do you initialize Sentry?

I will look into this, it seems to me there may be some conflict there. One thing you could try is to log this before calling Sentry.init():

console.log(globalThis.__SENTRY__);

Does this output something for you? 🤔

[Mintoo200]

Same issue here, migrating from configureScope() to getCurrentScope(). Adding console.log(globalThis.__SENTRY__); outputs nothing both in sentry.client.config.ts and sentry.server.config.ts.
Currently running node v20.12.0 and our config files can be found here for the client and for the server

[Lms24]

@Mintoo200 just to rule one thing out: Did you follow the migration guide for initializing the v8 SDK? I looked at your repo and couldn't find the instrumentation.js file that you need for NextJS with v8.

[Mintoo200]

Did you follow the migration guide for initializing the v8 SDK?

Indeed we did not, we relied on the changelog, which didn't mention it. I'll take a peek today, thanks for the pointer :)

I opened an issue for this: aandrewww/pino-sentry#68

Thanks !

[mydea]

@lcsvcn also for your original issue, I think the most likely cause is that there is somehow an older version of Sentry installed & used as well - could that be the case?

FWIW we are looking into ways to make this less likely to break, but in any case such a setup would always be subject to have problems, so this should be resolved in any case - there should always just be a single version of Sentry installed and run in your app!