@sentry/vue include httpClientIntegration

[giolf]

Problem Statement

Currently it seems is not possible to use the httpClientIntegration with '@sentry/vue' package:

  Sentry.init({
  ...
    integrations: [
      Sentry.browserTracingIntegration({ router }),
      Sentry.replayIntegration(),
      httpClientIntegration({...})
    ],
    ...
  })

Solution Brainstorm

Any ideas about it does not work? I get a type incompatibilities error

[mydea]

Hello,

do you have the exact same version of @sentry/integrations and @sentry/vue installed? Can you make sure in your lockfile that there is no other version of a @sentry/... package installed? You can delete your lockfile & node_modules folder and re-install, that should align all versions.

For the upcoming v8 release, you won't need @sentry/integrations anymore, but you'll be able to directly add this integration from @sentry/vue, which will hopefully make these kinds of version alignment issues go away!

[giolf]

Hi

npm show @sentry/vue version
7.105.0

npm install @sentry/integrations 7.105.0
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/7.105.0 - Not found
npm ERR! 404
npm ERR! 404  '7.105.0@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in: /Users/giovanni.far/.npm/_logs/2024-03-04T09_13_32_955Z-debug-0.log

[lforst]

@giolf Unfortunately that message is not really helpful to us. You likely have an npm proxy configured. Can you please check your lockfile for multiple different versions of sentry packages. Thank you!

[giolf]

@lforst I dont' have any proxy installed on top of npm.
@mydea raised up the fact of having the same version for @sentry/vue and @sentry/integrations ...
My version is 7.105.0 however that exact version does not exists for @sentry/integrations

in my lock file all sentry stuff has the same version, expect for @sentry/integrations because is uninstalled

[giolf]

uh wait, my bad typo in the npm install command. I found the version. I will give it a try and let u know if that fix it.

[giolf]

@mydea, @lforst
It seems to work, thanks a lot.
Quick question: it would be possible to show the stack trace in order to see from where the exception has been raised?

[lforst]

It seems to work, thanks a lot.

@giolf Cool. Closing this issue then!

Quick question: it would be possible to show the stack trace in order to see from where the exception has been raised?

We are tracking this here: #8353