-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Type 'ProfilingIntegration' is not assignable to type 'Integration' #10852
Comments
Hello! Are your versions in lockstep - meaning you also have |
Yes my package.json is using the same versions for both:
I'm guessing the issue is here:
|
Damn, good catch - sorry, that's a bug then! We'll fix this as soon as possible. |
Thanks for fixing this! Will the changes in #10861 be included in a release that we can use directly? |
I don't think #10865 fixed the issue unfortunately. I updated all my sentry packages to |
The dependencies should be correct now - can you delete your lockfile and try again? Chances are there is some leftover old version in there somewhere...? |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
I'm having the same issue, currently working with: "@sentry/node": "^7.116.0",
"@sentry/profiling-node": "^1.3.3", |
Starting in v8,
On v7, I recommend to delete your lockfile and re-install, probably there are some leftover old versions in there. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
7.103.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
This error is happening within a typescript project. It seems the
@sentry/profiling-node
package depends on an older version of@sentry/node
or@sentry/types
.Expected Result
No compile error
Actual Result
I get this error:
The text was updated successfully, but these errors were encountered: