Is Sentry.showReportDialog deprecated in @sentry/nextjs?
See original GitHub issueIssue
This an issue with:
Platform/SDK documentation (Which one?) https://docs.sentry.io/platforms/javascript/guides/nextjs/ Sentry Product (Which area?) nextjs
Description
I’m migrating from a mix of @sentry/node and @sentry/browser to the latest @sentry/nexjs plugin.
But one of the feature available in @sentry/browser
doesn’t seem to be available anymore (showReportDialog
).
Suggested Solution
Add documentation about whether it has been removed and how to use it with @sentry/nextjs
.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
sentry-javascript/CHANGELOG.md at master - GitHub
This release adds the withSentryConfig feature to the Svelte SDK. It replaces the now deprecated Svelte componentTrackingPreprocessor which will be removed ...
Read more >Next.js - Sentry Documentation
On this page, we get you up and running with Sentry's SDK, so that it will ... Sentry's Next.js SDK enables automatic reporting...
Read more >@sentry/nextjs - npm
Official Sentry SDK for Next.js. ... Start using @sentry/nextjs in your project by running `npm i @sentry/nextjs`. ... show deprecated versions. Version.
Read more >Update dependency @sentry/browser to v7 - GitLab.org
Removed usage of deprecated event.stacktrace field. (#4885); Removed raven-node backward-compat code (#4942); Removed showReportDialog ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @AbhiPrasad … doing the label dance. 😃
Yes we can add it to the backlog - we are aware of the issue and are working on a fix, should have updated the issue, thanks for the reminder @chadwhitacre