-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat(angular): Add Angular 14 support #5253
Conversation
Bump peer dependencies to Angular 14
size-limit report 📦
|
I'm not sure how you can be compatible with Angular 10 and Angular 14 at the same time without doing a compilation for View Engine and another for Ivy. Does that mean Angular 14 still ship |
Yes @alfaproject, upon compilation, the NG10-compiled SDK code is converted for NG14 compatibility (same as with 11-13). I know this is not the ideal solution but so far we haven't come up with a better one to enable Ivy support without conversion while maintaining compatibility with NG10. Very much open for suggestions and PRs though ;) EDIT: For more information, take a look at #4644 and #4641 on how we're currently compiling the Sentry Angular SDK |
Angular versions v2 to v11 are no longer under official support: Just wondering what's the reason to keep this support on your side. |
Yeah, Sentry should adopt and take advantage of Ivy. It would also address the following warning:
Since Angular 12 or 13, most Angular libs upgraded to Ivy and published an Ivy distribution with a major version bump because it is a breaking change. Here are a few examples and discussions from other open-source projects: mattlewis92/angular-calendar@29eb8c9 |
Hi @dzonatan and @nunoarruda thanks for your input, you're heard, I can assure you that :)
Our SDK philosophy is to be as backward-compatible as possible. When we first released I know that a lot of people upgrade their Angular versions regularly but - let's face it - there's also still quite some usage from older, LTS-discontinued versions.
I'd love to do that (and hence get rid of the warning) but given the above, we have to be sensible here. In any case, dropping support for an Angular version is a breaking change which means that we'll only be able to do this with the next major release of the SDK. Tell you what though: I'll bring this up with our team to discuss how we're going to handle this in the future, given that NG10 and 11 are not even supported by the Angular team anymore. In the meantime, I'll merge this to get Angular 14 supported for now. |
Is there a way of "getting our hands" at the version of the library, supporting Angular 14 (ahead of the next major release). Your current I'm aware that I could manually build a version from From my point-of-view, support for Sentry on "Angular 14" is currently "dead in water"? (so we've temporarily removed it from our app, which is obviously not a long-term viable solution). If I can do anything to "help out", regarding code-contributions, let me know... I just need someone to "point me in the direction of where to start" - thanks :) |
Hey @askarby, we released https://github.com/getsentry/sentry-javascript/releases/tag/7.2.0 a few hours ago today. Thanks a lot for your help offer, we highly appreciate it and will definitely need it in the future! 😄 Feel free to jump on a new version! :) |
This PR adds Angular 14 peer dependencies to
package.json
to make our SDK compatible with the recently released version 14 of Angular. Tested on an NG14 sample projects - Errors, transaction and component instrumentation work as expected.Fixes #5215