You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Sentry Webpack Plugin isn't as simple in Angular as in other frameworks: Before adding our plugin, users need to replace the default Angular builder w/ a custom builder.
Suggested Solution
While this arguably decreases the likelihood that people would use the plugin, we should nevertheless show them how they can use it.
The text was updated successfully, but these errors were encountered:
To ensure first-class compatibility with Angular's "new" rendering engine, Ivy, we needed to create a new SDK package that's compiled differently than the original `@sentry/angular` package. This new SDK is compatible with Angular 12 and newer and hence we're going to make it the default SDK in the docs going forward.
This PR
* Updates the Angular version <-> Sentry SDK compatibility description with a table
* I added entries for Angular 1/AngularJS (this came up recently in a Slack convo) and Angular 2-9 with a message that we do not support these versions anymore in v7 of the SDKs. Happy to make changes here if reviewers think this shouldn't be promoted.
* Updates imports and code snippets with versions for Angular 12+ (ivy) and Angular 10/11
* Updates the SDK onboarding wizard docs (+ Replay onboarding)
* Adds an Angular-specific verify code snippet which was missing before
* Adds file names to all angular code snippets (this came up in #6326 and it was easiest to just do it in this PR)
* streamlines the Angular "Getting started" page and fixes a few typos/wording issues
Co-authored-by: Andrea Canciani <[email protected]>
Co-authored-by: Liza Mock <[email protected]>
Core or SDK?
Platform/SDK
Which part? Which one?
@sentry/angular
Description
Following up on a recent customer call:
Using the Sentry Webpack Plugin isn't as simple in Angular as in other frameworks: Before adding our plugin, users need to replace the default Angular builder w/ a custom builder.
Suggested Solution
While this arguably decreases the likelihood that people would use the plugin, we should nevertheless show them how they can use it.
The text was updated successfully, but these errors were encountered: