-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CaptureConsole (and other integrations) specify an incorrect import name #1015
Comments
should be Sentry.Integrations.CaptureConsole note the s in integrations |
In Angular 6 I'm getting a signature mismatch error on integrations.
|
Still facing the same issue in Angular 8 |
Got the same issue in NestJS using
|
Same thing for me, the documentation was very confusing.
and
appeared. |
This will surely work in the case of Nodejs or anything:-
|
Sentry team, why don't you update the docs? They are old and people have to look into GitHub issues to integrate such a primary thing |
I think the problem here is that you've got a version mismatch between the |
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 label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
The
CaptureConsole
integration documentation specifies an "import name" ofSentry.Integration.CaptureConsole
. I'm not sure what this even means but there's no way it can be correct. My best guess at what it meant was this:This results in the following TypeScript error:
The proper way to import and configure it is:
All other integrations seem to be documented with "import names" in this manner.
The text was updated successfully, but these errors were encountered: